From: Andrew Haley <aph@redhat.com>
To: Jason Gross <jasongross9@gmail.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: ld cannot find -lffi
Date: Mon, 19 Aug 2013 07:54:00 -0000 [thread overview]
Message-ID: <5211CF37.1060103@redhat.com> (raw)
In-Reply-To: <CAKObCaqAXe-rpyVDDt0AMjAALT6U-VAOqpQzyyPYAEyriFf3vg@mail.gmail.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.
prev parent reply other threads:[~2013-08-19 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKObCao=vTWDD_chBr9vV2UB8MqMOqxLq5_03yzYfqbKzkV-1A@mail.gmail.com>
2013-08-17 4:23 ` Jason Gross
2013-08-17 9:08 ` Andrew Haley
2013-08-17 9:28 ` Jason Gross
2013-08-17 10:16 ` Andrew Haley
2013-08-17 13:40 ` Jason Gross
2013-08-19 7:54 ` Andrew Haley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5211CF37.1060103@redhat.com \
--to=aph@redhat.com \
--cc=jasongross9@gmail.com \
--cc=libffi-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).