From owner-freebsd-gnome@FreeBSD.ORG Sun Nov 17 14:15:36 2013 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E225C6FA; Sun, 17 Nov 2013 14:15:35 +0000 (UTC) Received: from fep19.mx.upcmail.net (fep19.mx.upcmail.net [62.179.121.39]) by mx1.freebsd.org (Postfix) with ESMTP id CFBE82005; Sun, 17 Nov 2013 14:15:34 +0000 (UTC) Received: from edge01.upcmail.net ([192.168.13.236]) by viefep19-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20131117141532.GPA18358.viefep19-int.chello.at@edge01.upcmail.net>; Sun, 17 Nov 2013 15:15:32 +0100 Received: from [127.0.0.1] ([178.84.132.32]) by edge01.upcmail.net with edge id qeFW1m0180i5fp601eFXJR; Sun, 17 Nov 2013 15:15:32 +0100 X-SourceIP: 178.84.132.32 Message-ID: <5288CF82.8000700@rainbow-runner.nl> Date: Sun, 17 Nov 2013 15:15:30 +0100 From: Koop Mast User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Gerard Seibert , freebsd-questions@freebsd.org Subject: Re: GNUPG fails to build on FreeBSD 10.0-BETA3 References: <001401cee259$074f0930$15ed1b90$@seibercom.net> <86iovsaayw.wl%hskuhra@eumx.net> <004501cee2c4$45339980$cf9acc80$@seibercom.net> <5287E018.9020701@rainbow-runner.nl> <014801cee39a$570e3260$052a9720$@seibercom.net> In-Reply-To: <014801cee39a$570e3260$052a9720$@seibercom.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 131116-1, 16-11-2013), Outbound message X-Antivirus-Status: Clean Cc: gnome@FreeBSD.org, "'Herbert J. Skuhra'" , kuriyama@FreeBSD.org, zeising@FreeBSD.org X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Nov 2013 14:15:36 -0000 On 17-11-2013 14:38, Gerard Seibert wrote: >> -----Original Message----- >> From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd- >> questions@freebsd.org] On Behalf Of Koop Mast >> Sent: Saturday, November 16, 2013 4:14 PM >> To: freebsd-questions@freebsd.org >> Cc: gnome@FreeBSD.org; 'Herbert J. Skuhra'; kuriyama@FreeBSD.org; >> zeising@FreeBSD.org >> Subject: Re: GNUPG fails to build on FreeBSD 10.0-BETA3 >> >> On 16-11-2013 13:06, Gerard Seibert wrote: >>>> -----Original Message----- >>>> From: Herbert J. Skuhra [mailto:hskuhra@eumx.net] >>>> Sent: Saturday, November 16, 2013 5:38 AM >>>> To: Gerard Seibert >>>> Cc: freebsd-questions@freebsd.org; kuriyama@FreeBSD.org >>>> Subject: Re: GNUPG fails to build on FreeBSD 10.0-BETA3 >>>> >>>> On Fri, 15 Nov 2013 18:18:43 -0500 >>>> Gerard Seibert wrote: >>>> >>>>> I have tried to build gnupg-2.0.22 on FreeBSD 10.0-BETA3 twice and >>>>> both attempts failed. This is a fresh install of FreeBSD on a >>>>> totally clean drive. This is the output at the end of the build attempt. >>>>> >>>>> checking for LIBFFI... no >>>>> configure: error: Package requirements (libffi >= 3.0.0) were not met: >>>>> >>>>> Package libffi was not found in the pkg-config search path. >>>>> Perhaps you should add the directory containing `libffi.pc' >>>>> to the PKG_CONFIG_PATH environment variable Package 'libffi', >>>>> required by 'world', not found >>>>> >>>>> Consider adjusting the PKG_CONFIG_PATH environment variable if you >>>>> installed software in a non-standard prefix. >>>> Subject is wrong! devel/glib20 fails to build, not security/gnupg! >>>> >>>> Does /usr/local/libdata/pkgconfig/libffi.pc exist? >>>> Have you tried to rebuild devel/libffi? >>> Okay, "libffi.pc" did not exist. "devel/glib20" was failing to build >>> and then subsequently "/security/gnupg" due to this fact. I built >> "devel/libffi" >>> and then preceded to building "gnupg". It is building now and appears to be >> going well. >>> Obviously, there is a dependency problem. Now, should I file a PR and if >> so, against which port? Since "devel/glib20" was not pulling in "libffi" I would >> assume "glib20" is the port to report. >>> Thanks for your assistance. >>> >> Like the PR stated, the problem is why it didn't find libffi. So libffi.pc doesn't >> excists glib20 doesn't know where to find it. So the next question would be >> why isn't libffi.pc there. Did you try Herbert's suggestion of rebuilding libffi? > Of course I manually built "libffi"; otherwise, I would not have been able to get the other ports built. My question is why "glib20" doesn't pull the port in and if I should file a PR against it. > It already does. It is already mentioned in LIB_DEPEND. LIB_DEPENDS implies that the mentioned ports are available during the build of the port. If there is a problem with the libffi port pkg-config file (libffi.pc) then glib20 configure step can't find libffi and fails. -Koop --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com