OK; I managed to get -CURRENT built yesterday, but the breakage I'm now seeing is ... different. It's not a matter of warnings, anyway:
cc -O -pipe -D__FBSDID=__RCSID -static -o yacc closure.o error.o lalr.o lr0.o main.o mkpar.o output.o reader.o skeleton.o symtab.o verbose.o warshall.o sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 yacc /usr/obj/usr/src/i386/usr/bin sh /usr/src/tools/install.sh -c -o root -g wheel -m 555 /usr/src/usr.bin/yacc/yyfix.sh /usr/obj/usr/src/i386/usr/bin/yyfix /usr/obj/usr/src/i386/usr/bin/byacc -> /usr/obj/usr/src/i386/usr/bin/yacc cd /usr/src/usr.bin/colldef; make obj; make depend; make all; make DESTDIR=/usr/obj/usr/src/i386 install /usr/obj/usr/src/i386/usr/src/usr.bin/colldef created for /usr/src/usr.bin/colldef yacc -d /usr/src/usr.bin/colldef/parse.y cp y.tab.c parse.c lex -t -8 -i /usr/src/usr.bin/colldef/scan.l > scan.c rm -f .depend mkdep -f .depend -a -I. -I/usr/src/usr.bin/colldef -I/usr/src/usr.bin/colldef/../../lib/libc/locale -DCOLLATE_DEBUG -DYY_NO_UNPUT -D__FBSDID=__RCSID parse.c scan.c cc: parse.c: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/usr.bin/colldef. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. CVSup history of late: freebeast(5.0-C)[7] tail /var/log/cvsup-history.log CVSup begin from cvsup14.freebsd.org at Wed May 8 03:47:02 PDT 2002 CVSup ended from cvsup14.freebsd.org at Wed May 8 03:53:48 PDT 2002 CVSup begin from cvsup14.freebsd.org at Wed May 8 12:03:54 PDT 2002 CVSup ended from cvsup14.freebsd.org at Wed May 8 12:10:35 PDT 2002 CVSup begin from cvsup14.freebsd.org at Thu May 9 03:47:02 PDT 2002 CVSup ended from cvsup14.freebsd.org at Thu May 9 03:53:44 PDT 2002 CVSup begin from cvsup14.freebsd.org at Fri May 10 03:47:02 PDT 2002 CVSup ended from cvsup14.freebsd.org at Fri May 10 03:56:26 PDT 2002 CVSup begin from cvsup14.freebsd.org at Sat May 11 03:47:02 PDT 2002 CVSup ended from cvsup14.freebsd.org at Sat May 11 03:54:26 PDT 2002 freebeast(5.0-C)[8] And yes, after the usual "cvs update," I saw that UPDATING was updated, saw the comment that reinforced obrien's message to -current yesterday about coping with CVS repository weirdness, and took the recommended action as a preemptive strike, so src/contrib/gcc should be clean -- though it appears I didn't get that far.... Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] Microsoft products -- for those times when reliability just doesn't matter. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
