From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31002 invoked by alias); 17 Aug 2013 09:08:52 -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 30988 invoked by uid 89); 17 Aug 2013 09:08:52 -0000 X-Spam-SWARE-Status: No, score=-8.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sat, 17 Aug 2013 09:08:51 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r7H98n17023764 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 17 Aug 2013 05:08:49 -0400 Received: from zebedee.pink (ovpn-113-26.phx2.redhat.com [10.3.113.26]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r7H98lEx006633; Sat, 17 Aug 2013 05:08:48 -0400 Message-ID: <520F3D9F.4020907@redhat.com> Date: Sat, 17 Aug 2013 09:08:00 -0000 From: Andrew Haley User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Jason Gross CC: libffi-discuss@sourceware.org Subject: Re: ld cannot find -lffi References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2013/txt/msg00153.txt.bz2 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.