Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.sdsmt.edu!news.mid.net!mr.net!chi-news.cic.net!newsxfer2.itd.umich.edu!tank.news.pipex.net!pipex!dispatch.news.demon.net!demon!jraynard.demon.co.uk!not-for-mail From: james@jraynard.demon.co.uk (James Raynard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: make world does make clean first -- why?? Date: 11 Jun 1996 08:57:16 -0000 Organization: A FreeBSD Box Lines: 56 Message-ID: <4pjcdc$rl@jraynard.demon.co.uk> References: <DstI3t.HE1@midway.uchicago.edu> NNTP-Posting-Host: localhost.demon.co.uk X-NNTP-Posting-Host: jraynard.demon.co.uk In article <DstI3t.HE1@midway.uchicago.edu>, Steve Farrell <spfarrel@midway.uchicago.edu> wrote: > >so after a 24 hour make world build which was almost finished, i had to >stop it to reboot because i was having a problem. i figured no problem, it'll >just pick up where it left off (i mean, every 10 minute compile works that >way, so why would a compile that probably took a week and half on the >computer it was conceived on work any differently, right?) Actually, I know of some programs (xview, pine) where make starts a build by doing a 'make clean'. >but no such luck. seems i needed the option -DNOCLEAN to prevent it from >deleting what it had been working on the past 24 hours. oops -- too late >now. gr... It's actually got past the 'lib-tools' stage, you can just do 'make all install' to pick up where it left off. >i'm sure there is a VERY good reason for this scheme. someone please tell >me (as i start another huge compile process... -- though i'll be doing a little >pruning i think...) what it is? The reason is that 'make world' is meant to start from scratch and rebuild everything, so that you can be sure that you are building with the latest version of the build tools, any obsolete directories have been deleted, all the depend targets are up to date, etc etc. There's been some discussion recently on the freebsd-current mailing list about whether this is as appropriate as it was in "the good old days" when a lot of work was being done on the build tools. (If you're running -current or -stable BTW, it's essential to subscribe to the appropriate mailing list so you can keep in touch). Personally, I usually just do a 'make all install' every day and do a 'make world' about once a week. >(this is my first dissappointment with freebsd, btw) You have my sympathies. Even though it only takes 5-6 hours on my machine, and I leave it running overnight, it's still too long for my liking 8-( >(that problem i was having that caused me to reboot, btw, was that >non-root shells couldn't fork any processes-- i figured that the >process table must have been near full... odd, b/c i thought 10 users >in kernel config meant up to 360 processes, and ps -aux showed not >nearly that many... so i was rebooting after building another -STABLE >kernel with that number pushed up to 40...) Shell limits? -- James Raynard, Edinburgh, Scotland james@jraynard.demon.co.uk jraynard@FreeBSD.ORG