solaris bootstrap failure using cc for stage1, stab.h not found...

[Kaveh R. Ghazi]

 > From: Jeffrey A Law <law@hurl.cygnus.com>
 > 
 >   In message < 199811171837.NAA27637@caip.rutgers.edu >you write:
 >   >  > From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
 >   >  >  
 >   >  >  > From: mrs@wrs.com (Mike Stump)
 >   >  >  > 
 >   >  >  > > From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
 >   >  >  > >       So we either need to:
 >   >  >  > > 
 >   >  >  > > 3.  Rerun configure for every stage.  (Possibly a large job.)
 >   >  >  >  
 >   >  >  > We only need to run it if the compiler changes, so twice should be
 >   >  >  > enough.  stagen, where n is >=2 are all the same compiler.
 >   >  >  
 >   >  >         Good point.  And we only need to rerun configure in the gcc
 >   >  > directory, not anywhere else.  It might not be that big of a job, if the
 >   >  > consensus is we should do this. 
 >   >  >                 --Kaveh
 >   > 
 >   > 	Here's a patch to implement this.  It solves the Solaris bootstrap
 >   > problem I reported in http://www.cygnus.com/ml/egcs-bugs/1998-Nov/0469.html
 >   > .
 >   > Shall I install it?
 >   > 
 >   > 		--Kaveh
 >   > 
 >   > 
 >   > Tue Nov 17 13:26:55 1998  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
 >   > 
 >   > 	* Makefile.in (reconfigure): New target to rerun configure using
 >   > 	the stage1 generated compiler.
 >   > 	(bootstrap): Run `$(MAKE) reconfigure' right after creating the
 >   > 	stage1 directory, but before building stage2.
 > 
 > I don't particularly like the idea of rerunning configure like this.  Can we
 > look for alternate ways to solve this problem?
 > jeff

	When you say: "the idea of rerunning configure like this", do
you mean you don't like the way I implemented it, or do you mean you
don't like the idea of rerunning configure between stage 1 & 2?

		--Kaveh
--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Icon CMT Corp.