On Fri, Jan 21, 2000 at 10:11:57AM -0800, Bill Swingle wrote:
> I updated my source tree around 10pm PST last night (01/20) and made
> world only to find it broken this morning. I reupdated my tree just now
> and it doesnt look like any files that might fix this have been touched.
> Anyone else seeing this?
>
> cc -pg -O -pipe -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 -c
>/usr/src/lib/libc/../libc/gen/wait3.c -o wait3.po
> cc -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.o
> 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
> *** Error code 1
> *** Error code 1
> 2 errors
> *** Error code 2
> 1 error
> *** Error code 2
> 1 error
> *** Error code 2
> 1 error
> *** Error code 2
> 1 error
> root@rooter:/usr/src$ cvs -Rq update -PdA
> U etc/MAKEDEV
> U etc/pccard.conf.sample
> U usr.sbin/pccard/pccardd/cardd.c
> U usr.sbin/pccard/pccardd/cardd.h
> U usr.sbin/pccard/pccardd/file.c
> root@rooter:/usr/src$
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?
In any case, doing a 'make includes' will get you past this.
Thanks,
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
