From owner-freebsd-questions@FreeBSD.ORG Mon Jan 19 14:08:54 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 836B816A4CE for ; Mon, 19 Jan 2004 14:08:54 -0800 (PST) Received: from rutger.owt.com (rutger.owt.com [204.118.6.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5436A43D41 for ; Mon, 19 Jan 2004 14:08:48 -0800 (PST) (envelope-from kstewart@owt.com) Received: from topaz-out (owt-207-41-94-233.owt.com [207.41.94.233]) by rutger.owt.com (8.11.6p2/8.9.3) with ESMTP id i0JM7u231788; Mon, 19 Jan 2004 14:07:56 -0800 From: Kent Stewart To: Nick Rogness Date: Mon, 19 Jan 2004 14:07:55 -0800 User-Agent: KMail/1.5.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401191407.55699.kstewart@owt.com> cc: freebsd-questions@freebsd.org Subject: Re: make buildworld fails X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2004 22:08:54 -0000 On Monday 19 January 2004 01:56 pm, Nick Rogness wrote: > On Mon, 19 Jan 2004, Kent Stewart wrote: > > On Monday 19 January 2004 11:55 am, Nick Rogness wrote: > > > On Mon, 19 Jan 2004, Kevin D. Kinsey, DaleCo, S.P. wrote: > > > > Nick Rogness wrote: > > > > >I cvsup'd just a few minutes ago and tried a make buildworld. > > > > > Any hints as to why I'm failing out? Details below: > > > > > > > > > >/usr/src/gnu/usr.bin/binutils/objdump/../../../../contrib/binu > > > > >tils /binutils/objdump.c:1553: unterminated character constant > > > > > mkdep: compile failed > > > > > > > > Yes ;-) > > > > > > > > There is an unterminated character constant in line 1553 of > > > > "objdump.c" in the directory given by the error message. > > > > > > > > Suppose there's a semicolon missing there? > > > > > > > > However, as Kent Stewart has noticed, it's a real good idea to > > > > make sure you're building the correct src tree first. AFAIK, > > > > 5.x is using different build tools. > > > > > > Forgot to mention, this is the 4 branch. > > > > All of the RELENG_4.... have the following line at objdump.c:1553 > > fatal (_("Can't use supplied machine %s"), machine); > > > > What do you have? That line has a matched pair of "'s. It sounds > > like you have a corrupted source. The usual fix is to delete it and > > recvsup. Since, you still really haven't told us what you cvsup'ed, > > you should include "in-line" a copy of your cvsup file, so that we > > know what we are trying to diagnose :). > > I cvsup'd the whole system from the stable-supfile > provided in /usr/share/examples/cvsup. That is what was ment by > 'the 4 branch' above. The entire source tree (RELENG_4) like I've > done thousands of times. Ah, but you could have been following RELENG_4_9, which is the security version of 4.9-release, or RELENG_4_9_0_RELEASE and etc. > > It appears to be dying in another place this time. I think it is > probably memory or some other hardware problem. Anybody had > this experience with hardware and building? That is a characteristic of bad hardware. FWIW, just in case you were following RELENG_4, I cvsup'ed RELENG_4 and successfully did a buildworld. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html