Date: Sat, 16 Nov 2013 22:14:00 +0100 From: Koop Mast <kwm@rainbow-runner.nl> To: freebsd-questions@freebsd.org Cc: gnome@FreeBSD.org, "'Herbert J. Skuhra'" <hskuhra@eumx.net>, kuriyama@FreeBSD.org, zeising@FreeBSD.org Subject: Re: GNUPG fails to build on FreeBSD 10.0-BETA3 Message-ID: <5287E018.9020701@rainbow-runner.nl> In-Reply-To: <004501cee2c4$45339980$cf9acc80$@seibercom.net> References: <001401cee259$074f0930$15ed1b90$@seibercom.net> <86iovsaayw.wl%hskuhra@eumx.net> <004501cee2c4$45339980$cf9acc80$@seibercom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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? -Koop --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5287E018.9020701>