From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 03:58:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CF1E1065686; Thu, 25 Sep 2008 03:58:35 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id D9A758FC0A; Thu, 25 Sep 2008 03:58:34 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD)) id 1Kihzu-00097K-8F; Wed, 24 Sep 2008 23:58:34 -0400 Date: Wed, 24 Sep 2008 23:58:34 -0400 From: Gary Palmer To: Jeremy Chadwick Message-ID: <20080925035834.GD60230@in-addr.com> References: <48DAF163.8060502@highperformance.net> <20080925034320.GA2985@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080925034320.GA2985@icarus.home.lan> Cc: "Jason C. Wells" , freebsd-stable Subject: Re: buildworld fails immediately X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2008 03:58:35 -0000 On Wed, Sep 24, 2008 at 08:43:20PM -0700, Jeremy Chadwick wrote: > On Wed, Sep 24, 2008 at 07:03:15PM -0700, Jason C. Wells wrote: > > I am trying to build RELENG_6. I receive the following errors. > > > > [root@s4cr /usr/src]# make buildworld > > "/dev/null", line 4: Need an operator > > "/dev/null", line 6: Need an operator > > "/dev/null", line 8: Need an operator > > "/dev/null", line 9: Need an operator > > "/dev/null", line 11: Need an operator > > "/dev/null", line 12: Need an operator > > "/dev/null", line 13: Need an operator > > "/dev/null", line 15: Need an operator > > "/dev/null", line 16: Need an operator > > "/dev/null", line 18: Need an operator > > > > > > I figured I got a partial update or something. Re-supping didn't help. > > I am building on 6.2-RELEASE inside a jail. Jails are new for me so > > maybe I missed something there. > > Your previous mail (Subject: CPUTYPE Now Required?) answers what's > happening quite clearly. Look closely at the -f argument being > passed to make. > > I cannot help you with jails, as I know nothing about them. But it > appears to me you have a very broken make.conf or build environment. Actually, this is in Makefile.inc1 _CPUTYPE!= MAKEFLAGS= CPUTYPE=${_TARGET_CPUTYPE} ${MAKE} \ -f /dev/null -m ${.CURDIR}/share/mk -V CPUTYPE (line 141 in my 6.3 era source tree) Which I think you'll find ends up with the make command the user posted in the other e-mail. Regards, Gary