This is the mail archive of the
libffi-discuss@sourceware.org
mailing list for the libffi project.
Re: ld cannot find -lffi
- From: Andrew Haley <aph at redhat dot com>
- To: Jason Gross <jasongross9 at gmail dot com>
- Cc: libffi-discuss at sourceware dot org
- Date: Mon, 19 Aug 2013 08:54:31 +0100
- 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> <CAKObCaro5A2SjYfkAZHgaWBMi8EhFTm6ZrHC07=BAVLPTE-_tQ at mail dot gmail dot com> <520F4D8C dot 1020201 at redhat dot com> <CAKObCaqAXe-rpyVDDt0AMjAALT6U-VAOqpQzyyPYAEyriFf3vg at mail dot gmail dot com>
On 08/17/2013 02:40 PM, Jason Gross wrote:
> On Sat, Aug 17, 2013 at 6:16 AM, Andrew Haley <aph@redhat.com> wrote:
>>
>> And what does
>>
>> gcc -print-multi-os-directory
>>
>> say?
>>
> Ah, indeed, that gives "../lib64". So I guess the .pc file should be
> set up to use multi_os_directory or toolexeclibdir?
Yes. I don't thunk anything good can happen if your libdir
doesn't correspond with your multi-os-directory. This is all
really to do with autoconf and libtool; there's nothing much
libffi can do about it.
Andrew.