On Sat, Dec 17, 2005 at 09:41:16PM -0500, Richard Kenner wrote: > bootstrap-lean is done by doing the following (which I feel is the > wrong way): > > Configure with --enable-bootstrap=lean > and then do a "make bootstrap" > > I agree with you. Why not just keep this as a make target? Why go back and > have to reconfigure?
This is a known shortcoming. We've been talking about how to change it. > And yes this causes to use different scripts for different versions of > gcc. > > I think that's a serious problem. I see no argument against upwards > compatibility here: it's all well and good to add new options to the toplevel, > but why remove ones from the gcc/ Makefile that have worked for decades and > people still use? Because the whole point of this process is to remove all the bootstrap logic from the gcc subdirectory, which is exactly where it doesn't belong. This will let us take major steps forward in our build process; one it's already taken is letting host libraries and tools (like libcpp) be bootstrapped along with the compiler. Another one it will take, soon, is letting target libraries be bootstrapped instead of the huge amount of cruft we have inside the gcc directory to handle libgcc. They've continued working for "decades" because up until now, no one's been brave enough to try to rework them :-) -- Daniel Jacobowitz CodeSourcery, LLC
