From owner-freebsd-ports@FreeBSD.ORG Sat Jul 26 10:14:55 2008 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 DBA441065671; Sat, 26 Jul 2008 10:14:55 +0000 (UTC) (envelope-from david@vizion2000.net) Received: from dns1.vizion2000.net (77-99-36-42.cable.ubr04.chap.blueyonder.co.uk [77.99.36.42]) by mx1.freebsd.org (Postfix) with ESMTP id 971508FC12; Sat, 26 Jul 2008 10:14:55 +0000 (UTC) (envelope-from david@vizion2000.net) Received: by dns1.vizion2000.net (Postfix, from userid 1007) id 95A641CC31; Sat, 26 Jul 2008 03:37:02 -0700 (PDT) From: David Southwell Organization: Voice and Vision To: freebsd-ports@freebsd.org Date: Sat, 26 Jul 2008 03:37:01 -0700 User-Agent: KMail/1.9.7 References: <200807241240.46520.david@vizion2000.net> <200807260145.12542.david@vizion2000.net> <488AF712.5020500@FreeBSD.org> In-Reply-To: <488AF712.5020500@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807260337.02301.david@vizion2000.net> Cc: "Philip M. Gollucci" , Remko Lodder Subject: Re: compile failure _www/mod_python3/work/mod_python-3.3.1. 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: Sat, 26 Jul 2008 10:14:56 -0000 On Saturday 26 July 2008 03:06:10 Remko Lodder wrote: > David Southwell wrote: > > structure or union > > apxs:Error: Command failed with rc=65536 > > . > > The error appears to be telling you that apxs doesn't support the thing > you want to do with it. Did you look into your apache build already? > > //Remko Strange you should say that because I was asking myself the same question. I am just doing a portupgrade -fr apache. I will report results when finished. David BTW I would have thought, if that is the case, that mod_python would have reported a dependency error. The other thing is that we were doing an upgrade from the earlier version which was working fine.. So I doubt whether that is the cause of the error. David