From: Jason Gross <jasongross9@gmail.com>
To: libffi-discuss@sourceware.org
Subject: ld cannot find -lffi
Date: Sat, 17 Aug 2013 04:23:00 -0000 [thread overview]
Message-ID: <CAKObCapWAdB-XMSU+X5+M2P6mMNjzuU9+y_in6WQ1rG=T3qF2g@mail.gmail.com> (raw)
In-Reply-To: <CAKObCao=vTWDD_chBr9vV2UB8MqMOqxLq5_03yzYfqbKzkV-1A@mail.gmail.com>
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"
Thanks,
Jason
next parent reply other threads:[~2013-08-17 4:23 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 [this message]
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
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='CAKObCapWAdB-XMSU+X5+M2P6mMNjzuU9+y_in6WQ1rG=T3qF2g@mail.gmail.com' \
--to=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).