This is the mail archive of the
libffi-discuss@sourceware.org
mailing list for the libffi project.
Re: ld cannot find -lffi
- From: Jason Gross <jasongross9 at gmail dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: libffi-discuss at sourceware dot org
- Date: Sat, 17 Aug 2013 05:27:44 -0400
- Subject: Re: ld cannot find -lffi
- References: <CAKObCao=vTWDD_chBr9vV2UB8MqMOqxLq5_03yzYfqbKzkV-1A at mail dot gmail dot com> <CAKObCapWAdB-XMSU+X5+M2P6mMNjzuU9+y_in6WQ1rG=T3qF2g at mail dot gmail dot com> <520F3D9F dot 4020907 at redhat dot com>
I did not pass --libdir. I ran `./configure
--prefix="$HOME/.local64/" && make -j16 && make install -j16`
-Jason
On Saturday, August 17, 2013, Andrew Haley wrote:
>
> On 08/17/2013 05:22 AM, Jason Gross wrote:
> > I have installed libffi-3.0.13 from source. The generated Makefile
> > tells me "toolexeclibdir = $(libdir)/../lib64", and the libraries seem
> > to have installed there. However, the .pc file that gets installed
> > tells pkg-config to tell ld to look in "libdir=${exec_prefix}/lib".
> > Hence, ld cannot find -lffi when I go to compile something with "gcc
> > `pkg-config --libs --cflags libffi`". I can workaround this by
> > copying the contents of lib64 to lib, but this seems silly and broken.
> > In addition to wanting this bug to be fixed, I'm curious to know
> > where the Makefile gets lib64 from, because "grep lib64 *" tells me
> > that the only other appearance is configure:
> > sys_lib_dlsearch_path_spec="/lib64 /usr/lib64 /lib /usr/lib" (also
> > makefiles.out~, but I figure that's a temporary). If it's relevant,
> > uname -a tells me "Linux cagnode17 2.6.32-5-xen-amd64 #1 SMP Sun Sep
> > 23 13:49:30 UTC 2012 x86_64 GNU/Linux"
>
> When you configured, what was your --libdir argument?
>
> Andrew.
>
>