GNUPG fails to build on FreeBSD 10.0-BETA3

[Koop Mast]

On 17-11-2013 14:38, Gerard Seibert wrote:
>> -----Original Message-----
>> From: owner-freebsd-questions at freebsd.org [mailto:owner-freebsd-
>> questions at freebsd.org] On Behalf Of Koop Mast
>> Sent: Saturday, November 16, 2013 4:14 PM
>> To: freebsd-questions at freebsd.org
>> Cc: gnome at FreeBSD.org; 'Herbert J. Skuhra'; kuriyama at FreeBSD.org;
>> zeising at 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 at eumx.net]
>>>> Sent: Saturday, November 16, 2013 5:38 AM
>>>> To: Gerard Seibert
>>>> Cc: freebsd-questions at freebsd.org; kuriyama at 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