From owner-freebsd-ports@FreeBSD.ORG Thu Feb 12 23:07:39 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5388216A4CE for ; Thu, 12 Feb 2004 23:07:39 -0800 (PST) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2F5343D1D for ; Thu, 12 Feb 2004 23:07:38 -0800 (PST) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i1D77Ve3057161 for ; Fri, 13 Feb 2004 18:07:32 +1100 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id i1D77VUs057160 for ports@freebsd.org; Fri, 13 Feb 2004 18:07:31 +1100 (EST) (envelope-from jeremyp) Date: Fri, 13 Feb 2004 18:07:31 +1100 From: Peter Jeremy To: ports@freebsd.org Message-ID: <20040213070731.GA57141@cirb503493.alcatel.com.au> References: <20040212104004.GA55768@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040212104004.GA55768@cirb503493.alcatel.com.au> User-Agent: Mutt/1.4.2i Subject: Re: XFree86-4 won't build on 4.9 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 07:07:39 -0000 On Thu, Feb 12, 2004 at 09:40:05PM +1100, Peter Jeremy wrote: >I've just wiped all my packages to do a clean rebuild and it has >failed virtually at the start: With an up-to-date /usr/ports and >non-existent /etc/make.conf, XFree86-4 won't build on >4.9-approximately-RELEASE. I checked against a (successful) build at work and found that my /usr/include/osreldate.h was setting __FreeBSD_version to 502101 instead of 490000. I've never run -current in that partition so I'm not exactly sure what happened. I'll use it as an excuse to upgrade to a more current stable. Thanks to Kent Stewart for confirming that it was a local error and sorry for the noise. Peter