Ok, Read through that. Now I'm getting the following after running the make buildworld:
[[snip]] cc -fpic -DPIC -O -pipe -mcpu=pentiumpro -DPTHREAD_KERNEL -I/usr/src/lib/libpthread/../libc/include -I/usr/src/lib/libpthread/thread -I/usr/src/lib/libpthread/../../include -I/usr/src/lib/libpthread/arch/i386/include -I/usr/src/lib/libpthread/sys -I/usr/src/lib/libpthread/../../libexec/rtld-elf -fno-builtin -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -Wall -I/usr/src/lib/libpthread/../libc/i386 -I/usr/src/lib/libpthread/thread -c /usr/src/lib/libpthread/arch/i386/i386/thr_switch.S -o thr_switch.So cc -fpic -DPIC -O -pipe -mcpu=pentiumpro -DPTHREAD_KERNEL -I/usr/src/lib/libpthread/../libc/include -I/usr/src/lib/libpthread/thread -I/usr/src/lib/libpthread/../../include -I/usr/src/lib/libpthread/arch/i386/include -I/usr/src/lib/libpthread/sys -I/usr/src/lib/libpthread/../../libexec/rtld-elf -fno-builtin -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -Wall -c /usr/src/lib/libpthread/sys/lock.c -o lock.So building shared library libkse.so.1 *** Error code 1 Stop in /usr/src/lib/libpthread. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. [[end snip]] Please help. TIA Eric F Crist AdTech Integrated Systems, Inc (952) 403-9000 -----Original Message----- From: Kent Stewart [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 26, 2003 8:02 PM To: Eric Crist Subject: Re: Make world problems from 4.9 to 5.1 On Wednesday 26 November 2003 05:45 pm, you wrote: > Are you referring to the: > > To get around the installworld problem, do: > #cd /usr/src/usr.bin/sed > #make install > #cd /usr/src > #make installworld > If that doesn't work, then try: > # make -k installworld > # make installworld There is a sequence that starts To upgrade in-place from 4.x-stable to current ---------------------------------------------- # 5.x uses more space than 4.x. Also, the location of kernel # modules has changed. If you are installing 5.0 onto a 4.x # system, you'll need about 30MB of free disk space on your / # partition. If you have less than this, you may encounter difficult # to back out of problems with this procedure. If /tmp is on # the / partition, you may want to completely remove all its content # before upgrading, as this can be a common source of shortage of # space on /. But I remember having a sequence where you had to do a -d and that isn't there any more. BTW, when they changed statfs on 5-current not too long ago, a make world would have rendered your system unbootable. I have a machine that is running 4-stable and because of the increased usage, I will do a clean install. Coral has a / with around 60-80 MB used and 5.x needs about 2x more and I have /var and /tmp as 1.5GB systems because I log everything from cvsup to "make index" and store the logs on /var/log/build. I have either /usr/src or /usr/obj 49% used on 1.5GB partitions. I suspect it is /usr/obj but it is running XP right now. I like more freespace and will have a 500MB /. I have /usr/src and /usr/obj on different controllers (IDE) so that I have concurrent I/O. If you use scsi, it doesn't matter as much. Kent > > Eric F Crist > AdTech Integrated Systems, Inc > (952) 403-9000 > > -----Original Message----- > From: Kent Stewart [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 26, 2003 7:24 PM > To: Eric Crist > Subject: Re: Make world problems from 4.9 to 5.1 > > On Wednesday 26 November 2003 04:44 pm, Eric Crist wrote: > > Hey all, > > > > I've got a Compaq Presario laptop with everything working great, > > except my wifi card. I've decided that I've been using 5.1 for a > > long > > > > time on my desktop without issue, so I want to upgrade my laptop. I > > can cvsup the sources fine, but when I enter into /usr/src and type > > make world, I get an error about checking the kernel to see if it's > > fresh enough and it dumps the core and exits. Is anyone else having > > this problem? I have tried doing a cd /usr/src; rm -rf * to delete > > everything in the /usr/src directory and rm -rf the /usr/obj > > directory. This has always worked for me in the past. > > > > Any enlightenment would be appreciated, even a point to the correct > > FM. > > There used to be a precise sequence that you had to follow to update > from 4.x to 5.x in UPDATING. Did you follow it? The last time I read > anything, a simple buildworld and etc. won't do it. > > Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"