From owner-freebsd-ports@FreeBSD.ORG Thu Nov 17 20:41:13 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 833A6106564A; Thu, 17 Nov 2011 20:41:13 +0000 (UTC) (envelope-from wietse@porcupine.org) Received: from spike.porcupine.org (spike.porcupine.org [IPv6:2604:8d00:189::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1A6948FC1A; Thu, 17 Nov 2011 20:41:13 +0000 (UTC) Received: by spike.porcupine.org (Postfix, from userid 1001) id 3SkvVw2ZYzzk2RT; Thu, 17 Nov 2011 15:41:12 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=porcupine.org; s=dktest; t=1321562472; bh=t4sw2d/kHgoAk5FpkgqWvgBrg1qZJdW5+PeHJMvzsxg=; h=Subject:In-Reply-To:To:Date:Sender:From:CC:MIME-Version: Content-Transfer-Encoding:Content-Type:Message-Id; b=DkQQDXAkVBMyme3X6r1tEvCmVY4KNeKQi/mBPKShBjK2qm/R86GfEbXN9Byssbp9A sMojhXisjmMl0c7OiSVSVLGYinhQLQMjkYQas1kvrS4WZIRj+/R9I42DkkpPPX4TET XSCMEilhAsU5JGQU9ig50jWjlUz6mCaqZoNqJNiw= In-Reply-To: <1321560805.6735.15.camel@hood.oook.cz> To: pav@FreeBSD.org Date: Thu, 17 Nov 2011 15:41:12 -0500 (EST) Sender: wietse@porcupine.org From: Wietse Venema X-Mailer: ELM [version 2.4ME+ PL124d (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Message-Id: <3SkvVw2ZYzzk2RT@spike.porcupine.org> Cc: Wietse Venema , Sahil Tandon , Renato Botelho , Jase Thew , Kurt Jaeger , freebsd-ports@FreeBSD.org, Chris Rees Subject: Re: "postfix-current" broken on amd64 platform X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2011 20:41:13 -0000 Pav Lucistnik: > Wietse Venema p??e v ?t 17. 11. 2011 v 13:23 -0500: > > 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. > > This is interesting. > > The build jails are configured to have only IPv4 address on lo0, > but the host have both IPv4 and IPv6 configured on its lo0. > > Changing the jail configuration is possible but if a reasonable > workaround can be made in postfix-current port I'd prefer not to touch > pointyhat configuration (unexpected consequences and all that...) I can competely fix this specific error instance with a one-line config file change, but I don't want to end up in the same boat again when some other program needs to be run during build time. A more proactive workaround would be to treat "protocol not supported" as a non-fatal error, just like "address family not supported" is. Please let me know if this works in the build cluster. It will log a warning but that should be justfied, because the system does have an abnormal configuration. Wietse *** src/util/inet_proto.c- Tue Jan 8 15:36:13 2008 --- src/util/inet_proto.c Thu Nov 17 08:49:31 2011 *************** *** 219,225 **** pf->dns_atype_list = make_unsigned_vector(3, T_A, T_AAAA, 0); pf->sa_family_list = make_uchar_vector(3, AF_INET, AF_INET6, 0); break; ! } else if (errno == EAFNOSUPPORT) { msg_warn("%s: IPv6 support is disabled: %m", context); msg_warn("%s: configuring for IPv4 support only", context); /* FALLTHROUGH */ --- 219,225 ---- pf->dns_atype_list = make_unsigned_vector(3, T_A, T_AAAA, 0); pf->sa_family_list = make_uchar_vector(3, AF_INET, AF_INET6, 0); break; ! } else if (errno == EAFNOSUPPORT || errno == EPROTONOSUPPORT) { msg_warn("%s: IPv6 support is disabled: %m", context); msg_warn("%s: configuring for IPv4 support only", context); /* FALLTHROUGH */