Date: Mon, 04 Sep 2000 19:31:48 -0400 From: Bill Moran <wmoran@columbus.rr.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: problems with make world (Sunday) Message-ID: <39B430E4.DA0D6B66@columbus.rr.com> References: <Pine.SOL.3.91.1000904183655.11049B-100000@travelers.mail.cornell.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Personally, I'm having nothing but grief! This is one of those odd times when I figured ... "I never have any trouble upgrading via cvsup ... I'll just do it now" (on a production machine) Well ... step one is to smack myself for being stupid, step two is to get this machine working correctly again, step 3 is to never EVER do anything this stupid again. If anyone is curious, or has any ideas what's wrong ... here are the symptoms: 1. I cvsupped to current 4.1-STABLE from 4.0-STABLE(June 3) 2. make buildworld 3. Attempted to compile a kernel ... lots-o-errors cd /usr/src/sys/i386/conf;/usr/sbin/config MYKERNEL All manner of complaints of errors in the kernel config file 4. Tried to do cd /usr/src;make buildkernel error: no such target (Here's where frustration and lack of sleep bred superior stupidity) 5. make installworld (I have no idea what I was thinking at this point ...) Of course ... now I can't do a ps, or top or anything like that ... the machine is still responding and doing its job (as a web server) So I'm super lucky on that point. Anyway, I tried recreating new config file from GENERIC, but I'm looking at GENERIC and it's dated March 1??? What's that about. I'm going to cvsdown to 4.0-STABLE and try to rebuild world - we'll see what happens ... -Bill nop1@cornell.edu wrote: > > Hi again, > > I did another cvsup (several, in fact) before posting my first message. I > also tried "make buildworld" several times after the first build failed. > Of course, I removed obj directory in a manner similar to what was > suggested by some of you each time. I am using a very simple script that > automates the build from freebsddiary.org > > Yes, it is the build that fails, not the install. If I remember correctly, > the build does not even finish building all the stuff in the tools stage > (but proceeds for a long time with no errors). I guess you'll have to wait > until I am done with my work for the day and get back to the > (non-networked) machine on which I have the build logs and post excerpts > from them. > > My only guess at this point is that I managed to not have some C/C++ > libraries installed... Well, FreeBSD 4.0 install from the CD set is quite > buggy, given that there are 4 CDs and some of the packages/distributions > on the first CD are dependent on packages on other CDs and fail to install > from the /stand/sysinstall, not even prompting you for the other CD. So > that could have happened. I am still hunting down various components > across CDs and adding them with pkg_add. > > -j4 should only affect number of simultaneous processes. Since I have a > dual-processor machine, I may try -j8. > > Thanks for assuring me that the branch is not broken. I was about to ditch > FreeBSD with disgust thinking that "these losers even have their stable > branch broken...". Just kidding! > > Nikita. > > On Mon, 4 Sep 2000, Erick Mechler wrote: > > > Try doing this: > > > > 1. do another cvsup to make sure that you got everything (and yes, using > > RELENG_4 will give you the latest -STABLE in the 4.x branch). > > 2. cd /usr/src > > 3. make -j4 buildworld > > 4. iff no errors, do make -j4 installworld > > > > You shouldn't have any problems with this, since I just did a sup this > > morning and the world built fine. > > > > BTW, I would highly recommend not using "make world", since this does the > > build and install all at once. If things go wrong during the build, you > > won't have a chance to fix them before the world is installed. By > > splitting them up with buildworld and installworld, you give yourself the > > chance to fix buildworld problems before you install them. > > > > Also note that to upgrade your kernel (which you have to do every time > > you do an installworld), continue on as such: > > > > 5. cd /usr/src/sys/i386/conf > > 6. cp GENERIC <your_kernel_here> > > 7. Edit <your_kernel_here> to your liking (be sure to check out > > /usr/src/sys/i386/conf/LINT which has all the possible config options. > > 8. cd /usr/src/ > > 9. make -j4 buildkernel > > 10. iff no errors, make -j4 installkernel > > > > The notes say to drop to single user before you do installworlds, but I > > haven't had any problems doing them in multiuser mode (besides, I don't > > have a console on my BSD machine, so single user is pretty difficult). > > > > Good luck, and let me know if you have any problems. > > > > Regards, > > Erick > > > > At Mon, Sep 04, 2000 at 05:13:50PM -0400, Nikita Proskourine said this: > > :: Hi all, > > :: > > :: I am a newbie to FreeBSD development, so please bear with me. I am > > :: currently using FreeBSD-4.0 RELEASE. I did a fresh cvsup (using RELENG_4 > > :: tag, that would get me a stable branch, right?) and "make world" on Sunday > > :: and the build failed somewhere in objc contribs for gcc. > > :: > > :: I made logs of the build and will send them later today. In the meantime, I > > :: was wondering if this is a known problem and whether there are workarounds > > :: for this. > > :: > > :: Nikita. > > :: > > :: > > :: To Unsubscribe: send mail to majordomo@FreeBSD.org > > :: with "unsubscribe freebsd-stable" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39B430E4.DA0D6B66>