On Mon, Mar 17, 2003 at 03:10:08AM -0800, Doug Barton wrote: > Are you guys precisely following the instructions in src/UPDATING? most definately, the new compiler depends on new syscalls in the kernel, and the kernel depends on new options in the compiler. I could not find anything about this situation in UPDATING.
I'm doing a fresh checkout of the -current tree while I'm writing this. I believe the procedure I followed was cvs co src -t . gperf rebuild bombed due to missing includes.. went ahead and tried make buildworld bombed on tar is a directory during the clean phase.. wasted my obj directory.. rm -rf /usr/obj cd /usr/src && make buildworld and bombed on rm -f tar addext.o argmatch.o backupfile.o basename.o dirname.o error.o exclude.o full-write.o getdate.o getline.o getopt.o getopt1.o getstr.o hash.o human.o mktime.o modechange.o prepargs.o print-copyr.o quotearg.o safe-read.o save-cwd.o savedir.o unicodeio.o xgetcwd.o xmalloc.o xstrdup.o xstrtoul.o xstrtoumax.o buffer.o compare.o create.o delete.o extract.o incremen.o list.o mangle.o misc.o names.o rtapelib.o tar.o update.o tar.1.cat rm: tar: is a directory *** Error code 1 this is of course todays current as of 5:30 a.m CST Rob > > On Mon, 17 Mar 2003, Scott Sipe wrote: > > > I second that problem. Tried doing an upgrade yesterday, and it didn't > > work--missing libc.so.4 error given during make installworld. > > > > Scott > > > > ----- Original Message ----- > > From: "Robert Garrett" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Sunday, March 16, 2003 3:53 AM > > Subject: source upgrade broken? > > > > > > > Gentleman, > > > > > > Please correct me if I am wrong but it appears, that the source upgrade > > > path from 4.* to 5.0 is broken. I havent played with it much but it > > appears thatbuilding the kernel, depends on somethings new to the -current > > compiler, and the compiler is dependant on stuff in the 5.-current kernel. I > > realize that with all the stuff thats been ripped out of 5.0 and added, that > > a clean install is probably the best way to go. I am just curious if it > > truly is borked or if it is just me. > > > > > > Robert Garrett > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > > > -- > > This .signature sanitized for your protection > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
