Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sun-barr!cs.utexas.edu!natinst.com!hrd769.brooks.af.mil!not-for-mail
From: burgess@hrd769.brooks.af.mil (Dave Burgess)
Newsgroups: comp.os.386bsd.questions
Subject: Re: buildworld.sh prob with cc
Date: 3 Apr 1993 12:55:30 -0600
Organization: Armstrong Lab MIS, Brooks AFB TX
Lines: 51
Message-ID: <1pkmj2INN4u0@hrd769.brooks.af.mil>
References: <C4vDEu.38D@news.water.ca.gov> <C4vnHI.rA@agora.rain.com>
NNTP-Posting-Host: hrd769.brooks.af.mil
In article <C4vnHI.rA@agora.rain.com> rgrimes@agora.rain.com (Rodney Grimes) writes:
>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.
To help others that are trying to do this, some of the errors that I
encountered when I started buildworld.sh were:
1. All of the subdirectories in cc should have the Makefile.symlinks
run in them. The spooky thing is that the first time through, they don't
get done, but the subsequent tries all work correctly. To solve the problem
(until the new patchkit comes out), before you run buildworld.sh, try the
following untested suggestion:
cd /usr/src/usr.bin/gcc
foreach i (`ls -l | grep '^d' | awk '{print $8}`)
cd $i
make -f /usr/src/usr.bin/gcc/Makefile.symlinks
cd /usr/src/usr.bin/gcc
end
Note that This is the brute force method. There are probably a dozen slicker
ways to do this.
2. The tn3270 directory does not make correctly. There is some debate
on what to do about this, but for now, I suggest you just take it out of
the Makefile that tries to make it.
3. One of the g++ libraries does not build correctly. I just commented it
out of the library Makefile. I will get to it later.
Note that each of these error will stop the 'make' that is started in
buildworld.sh. If you are not paying attention, you can end up with a
whole bunch of bad makes that have not run through the complete list.
>>Did I miss any caveats with buildworld.sh?
Oh well, you knew the job was dangerous when you took it, Fred.
--
------
TSgt Dave Burgess
NCOIC AL/Management Information Systems Office
Brooks AFB, TX