walt wrote: > > When compiling libc I see several of these 'sort' errors: > > cc -O -pipe -mcpu=pentiumpro -DLIBC_MAJOR=5 -I/usr/src/lib/libc/include > -I/usr/src/lib/libc/../../include -D__DBINTERFACE_PRIVATE -DINET6 > -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale > -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -DYP -DHESIOD -c > /usr/src/lib/libc/string/wmemset.c -o wmemset.o > building static c library > sort: open failed: +1: No such file or directory
Okay, I found out that you won't see these during a buildworld unless libc actually gets recompiled, which won't happen unless libc sources get modified. To force these errors to appear just 'cd /usr/src/lib/libc' and 'make clean' then 'make'. By doing a 'make -n' I found that this is the statement which produces the error: ar cq libc.a `lorder fork.o read.o chmod.o getpid.o mount.o wmemset.o | tsort -q` (For clarity I snipped a huge list of .o files from the middle of that statement.) There are several other similar statements that cause the same error message. So whaddya think? Is this an error to worry about? Or not. BTW, you can reproduce the error message by typing 'sort +1'. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message