From owner-freebsd-current Fri Jan 21 20:35: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 291C8156B1 for ; Fri, 21 Jan 2000 20:34:51 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 28994 invoked from network); 22 Jan 2000 04:34:42 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 22 Jan 2000 04:34:42 -0000 Date: Sat, 22 Jan 2000 15:34:40 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Jason Evans Cc: Bill Swingle , current@FreeBSD.ORG Subject: Re: even more breakage in current In-Reply-To: <20000121142251.D27689@sturm.canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Jan 2000, Jason Evans wrote: > On Fri, Jan 21, 2000 at 10:11:57AM -0800, Bill Swingle wrote: >... > > cc -DPROF -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -I/usr/src/lib/libc/i386 -c /usr/src/lib/libc/../libc/i386/gen/_setjmp.S -o _setjmp.po > > /tmp/ccg65684.s: Assembler messages: > > /tmp/cco65681.s: Assembler messages: > > /tmp/cco65681.s:361: Error: invalid character '(' in opcode > > /tmp/ccg65684.s:361: Error: invalid character '(' in opcode This happens when libc/i386/DEFS.h and libc/i386/gen/setjmp.S are current (as of Jan 21) but is out of date. > I moved some definitions from src/lib/libc/i386/DEFS.h to > src/sys/i386/include/asm.h. If the build system is looking at the > installed version of asm.h rather than the version in the source tree, this > error will occur. I did a 'make includes' during my testing, so I didn't > have this problem. > > It's my understanding that the build system is supposed to be sophisticated > enough to avoid such bootstrapping issues, but I don't understand it all > that well. Can someone explain whether this is a bug in the build system, > or if I should be doing something different? Everything should just work in this case, provided is up to date. All you could do better is commit first so that there is no window of inconsistency. > In any case, doing a 'make includes' will get you past this. Don't use `make includes' unless you are familiar enough with the build system not to need it. It _causes_ problems like this by defeating the build system (it gives a set of includes that tends not to match the libraries). It happens to fix the problem in this case (at least if you install only ). Test header changes using `NOCLEAN=1 make buildworld'. NOCLEAN is now fairly robust. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message