------- Comment #23 from skunk at iskunk dot org 2006-08-07 06:43 ------- (In reply to comment #21) > I'd only add that the upcoming GCC 4.2 release will feature a new bootstrap > procedure (aka toplevel bootstrap) that could solve the issue.
Very interesting. I'll have a look at it. If this refactors the rat's nest of Make variable overrides in the top-level makefile, then it could be a very good thing indeed. > On the one hand, and without any inflated ego :-), you cannot consider that > bootstrapping a compiler is like building any other piece of software. Very true, but in the simplest, degenerate case (bootstrapping with host == build == target), you could reasonably expect stage 1 (and anything before it) to be built with CC+CFLAGS. Principle of least surprise, and all that. (This is saying nothing about matching the triplets to CFLAGS, which does remain an issue. Yes, you can't be *completely* naive in building GCC.) > On > the other hand, the aforementioned toplevel bootstrap is aimed at eliminating > the peculiarities you noticed; for example, a bare "make" will automatically > perform a complete 3-stage bootstrap for a native compiler in the sense that > the end result should not depend on the bootstrap compiler anymore at all. I think you meant to say, "not depend on the native compiler" :-) But this is good---doing a bootstrap unconditionally is reasonable nowadays, and it should simplify the build system a bit (one less case to handle). (In reply to comment #22) > I'd also challenge this assertion: I don't think you can generically tweak > CFLAGS, in particular change the ABI, once a package has been configured. Right, but... of course, whenever I say that I set such-and-such flags, I mean before configure time. After that point, it usually doesn't matter what you have set in the environment, because the standard variables are explicitly assigned in the makefiles. (You didn't think I was asking for the build system to track variables in the environment _after_ configure time... did you?) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28515
