From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9524 invoked by alias); 17 Aug 2013 09:28:17 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 9515 invoked by uid 89); 17 Aug 2013 09:28:16 -0000 X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2 Received: from mail-pb0-f51.google.com (HELO mail-pb0-f51.google.com) (209.85.160.51) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sat, 17 Aug 2013 09:28:16 +0000 Received: by mail-pb0-f51.google.com with SMTP id jt11so2916627pbb.38 for ; Sat, 17 Aug 2013 02:28:14 -0700 (PDT) X-Received: by 10.68.226.7 with SMTP id ro7mr2155096pbc.72.1376731694532; Sat, 17 Aug 2013 02:28:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.103.41 with HTTP; Sat, 17 Aug 2013 02:27:44 -0700 (PDT) In-Reply-To: <520F3D9F.4020907@redhat.com> References: <520F3D9F.4020907@redhat.com> From: Jason Gross Date: Sat, 17 Aug 2013 09:28:00 -0000 Message-ID: Subject: Re: ld cannot find -lffi To: Andrew Haley Cc: libffi-discuss@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-SW-Source: 2013/txt/msg00154.txt.bz2 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. > >