Date: Thu, 17 Nov 2011 13:23:10 -0500 (EST) From: Wietse Venema <wietse@porcupine.org> To: Wietse Venema <wietse@porcupine.org> Cc: Sahil Tandon <sahil+freebsd-ports@tandon.net>, Renato Botelho <garga@freebsd.org>, Jase Thew <freebsd@beardz.net>, Kurt Jaeger <lists@opsec.eu>, freebsd-ports@FreeBSD.org, Chris Rees <utisoft@gmail.com> Subject: Re: "postfix-current" broken on amd64 platform Message-ID: <3SkrRf563xzk2RT@spike.porcupine.org> In-Reply-To: <3SkkT66wwmzk2RT@spike.porcupine.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Wietse Venema: > Jase Thew: > > It can occur when IPv6 is enabled, but you don't have any IPv6 addresses > > configured on any interfaces. (Yes, having an IPv6 enabled interface > > with no addresses assigned is non-RFC3513 compliant, but it can and does > > occur). ... > Thanks, this is very helpful. That code has not changed in 6 years, > so we are looking at an incompatible change in build environment. Actually, a Postfix built-in default setting changed on 20110918. It now enables IPv6 unless this is turned off in a configuration file. I can fix that at compile time, and thereby not trigger the error on build systems with unexpected IPv6 configurations. Wietse
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3SkrRf563xzk2RT>