This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: At last: the bool problem seems to be due to omitted dependencyfrommake check*
- From: Tim Josling <tej at melbpc dot org dot au>
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 02 Mar 2003 09:11:54 +1100
- Subject: Re: At last: the bool problem seems to be due to omitted dependencyfrommake check*
- Organization: Melbourne PC User Group
- References: <Pine.LNX.4.33.0303011620410.1914-100000@kern.srcf.societies.cam.ac.uk>
"Joseph S. Myers" wrote:
>
> On Sat, 1 Mar 2003, Tim Josling wrote:
>
> > The problem I had in this case was that the system cc didn't like -fstats so
> > it failed. To me, the stdbool only seems to solve part of the problem, which
> > is that suddenly we are building part of the compiler with a wrong compiler.
> > How would this work with C++?
>
> Both problems should be solved, but the dependency one is intrinsically
> hard to solve. After all, if you change toplev.c, it should first rebuild
> to stage1 toplev.o with the bootstrap compiler, then relink the stage1
> compiler, then rebuild stage2 and stage3, if the dependencies are properly
> correct. Properly correct dependencies should mean exposing all
> dependencies, between all stages, to one invocation of make, but this
> can't work because each stage needs to be built separately, with the files
> in the same location (not in the stage subdirectory), for the compare
> stage to succeed.
>
> --
> Joseph S. Myers
> jsm28 at cam dot ac dot uk
It looks like this is not going to get fixed. How about a patch to the
install.texi to at least warn people "make sure your build is up to date, e.g.
by make quickstrap, before starting any tests"?
Tim Josling