This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: solaris bootstrap failure using cc for stage1, stab.h not found...
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: solaris bootstrap failure using cc for stage1, stab.h not found...
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 11 Aug 1999 02:25:13 -0600
- cc: gcc-patches at egcs dot cygnus dot com, schwab at issan dot cs dot uni-dortmund dot de
- Reply-To: law at cygnus dot com
In message <199811171837.NAA27637@caip.rutgers.edu>you write:
> > 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.
This is going to make life a living hell on those of us who have to debug
codegen bugs in 3-stage bootstraps. We really need the ability to mix and
match .o files between stages and to be able to use *any* suitable host
compiler during any stage when tracking down staged codegen problems.
I'd really prefer not to go down the road of rerunning configure. I just
do not think it's really necessary and it just makes are life much more
difficult than it needs to be.
jeff