From owner-freebsd-ports@FreeBSD.ORG Tue Nov 15 16:51:34 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 874421065674; Tue, 15 Nov 2011 16:51:34 +0000 (UTC) (envelope-from freebsd@beardz.net) Received: from svr06-mx.btshosting.co.uk (mx-2.btshosting.co.uk [178.63.196.248]) by mx1.freebsd.org (Postfix) with ESMTP id 3AABE8FC0A; Tue, 15 Nov 2011 16:51:33 +0000 (UTC) Received: from [192.168.1.65] (027ecff8.bb.sky.com [2.126.207.248]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by svr06-mx.btshosting.co.uk (Postfix) with ESMTPSA id F1C1041B38; Tue, 15 Nov 2011 16:32:02 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=beardz.net; s=default; t=1321374723; bh=8sITB7Gd+NQFQfzzwwhW2MlGSQs37WDSJ/nk3nF/Zrg=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=gglBCWVDgr/2REMI6eBLDHswCSOXgQACtioVLedsAU/wL2qSJthwkQ2CvyyoNzdDl hLucICqdH6gumOx4fWkYD2F0O1lJHlapVFU4rLqD5RfL08lc/3sfaxtav6I8KiXNYc qymawlUj3AbpAxFGoBGvFEX+SA7oGGpFNtzOw9no= Message-ID: <4EC293FF.2000607@beardz.net> Date: Tue, 15 Nov 2011 16:31:59 +0000 From: Jase Thew User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Sahil Tandon References: <20111114083713.29fbecda@scorpio> <20111115022430.GA19970@magic.hamla.org> <1321350319.84509.2.camel@hood.oook.cz> <2859B9B3-0A75-40FD-B444-8885A6589A37@tandon.net> In-Reply-To: <2859B9B3-0A75-40FD-B444-8885A6589A37@tandon.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "eadler@FreeBSD.org" , "swills@FreeBSD.org" , "gjb@FreeBSD.org" , "freebsd@beardz.net" , "pav@FreeBSD.org" , "freebsd-ports@FreeBSD.org" 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: Tue, 15 Nov 2011 16:51:34 -0000 On 15/11/2011 14:31, Sahil Tandon wrote: > It was marked broken on a particular architecture, hence the genesis of this thread. I appreciate that diagnosis is difficult; perhaps Olli's suggestion is helpful in isolating the issue. I do not know how else to troubleshoot since these pointyhat errors are not - AFAIK - reproducible by others, on either i386 or amd64 platforms. Hi all, The install is failing during a call to $wrksrc/conf/post-install. Taken from the pointyhat logs : ./postconf -d) |egrep -v '^(myhostname|mydomain|mynetworks) ' >../../conf/main.cf.default ./postconf: fatal: socket: Protocol not supported Postconf is dying with a fatal socket error. This binary is used in various places, including $wrksrc/conf/post-install. There are various tests in this post-install script that will exit with 1 should executing postconf fail for any reason. Therefore, fixing the reason for postconf throwing a fatal error will fix the build/install. What networking/DNS configuration is Pointyhat lacking (or have sufficiently different to break the socket code inside of postconf)? Regards, Jase Thew.