"postfix-current" broken on amd64 platform

[Sahil Tandon]

On Nov 16, 2011, at 11:24 AM, Chris Rees <utisoft at gmail.com> wrote:

> On 16 Nov 2011 16:00, "Wietse Venema" <wietse at porcupine.org> wrote:
>> 
>> Kurt Jaeger:
>>> Hi!
>>> 
>>>>>>>>  Postconf opens a socket to determine the mynetworks value
> (it
>>>>>>>>  determines the local interfaces and their netmasks).
>>> [...]
>>>> Postfix does none of that.
>>> 
>>> The fbsd postfix-current port during the post-install script does
>>> something which fails on a jail-based build-cluster where the
>>> jail itself has no network connectivity.
>> 
>> Would it be possible to give the jail a loopback interface?
>> 
>> I don't mind if FreeBSD improves its build environment such that
>> it breaks the build after 12 years. If adding a loopback interface
>> fixes this, then we can all move on to more interesting things.
>> 
>>       Wietse
>> 
> 
> Clamav uses loopback on its testing phase, and works fine on the build
> cluster.

What irks me is that all other Postfix versions (that also call postconf) have no problem building/installing on the cluster.