Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!usenet.ee.pdx.edu!pdxgate!parsely!agora!rgrimes From: rgrimes@agora.rain.com (Rodney Grimes) Newsgroups: comp.os.386bsd.questions Subject: Re: buildworld.sh prob with cc Message-ID: <C4vnHI.rA@agora.rain.com> Date: 2 Apr 93 22:22:29 GMT Article-I.D.: agora.C4vnHI.rA References: <C4vDEu.38D@news.water.ca.gov> Organization: Open Communications Forum Lines: 24 stevec@water.ca.gov (Steve Croft) writes: >I have a new installation upon which I installed the dist files (bin, src, etc). >Got them going, then installed Patchkit 0.2.2. All was fine until I ran >"buildworld.sh". It appears that cc became hosed (the error was a prob with >"cc1" - my memory is failing). There are about 4 or 5 other bugs in the source tree that will cause buildworld.sh to fail at various places. I did not exam the output close enough when I ran the regression tests on buildworld.sh. There are several new patches coming in patchkit 0.2.3 that fix this. Regression testing on a new version of buildworld.sh just completed this morning. THe patchkit team is starting to package up 0.2.3, should begin alpha site testing some time next week, and a beta release the week after that. Note that this is all *RUMOR* from a real good source.. >Did I miss any caveats with buildworld.sh? >steve -- Rod Grimes rgrimes@agora.rain.com Accurate Automation Company All opinions belong to me and my company! Get your free copy of 386bsd from agate.berkeley.edu:/pub/386BSD via ftp! An out of work contractor... You need unix work done.... Send me your project!