Eric, Yes, I got that from the README. What I was looking for was a *shortcut*, ie: I compile ~1000 packages, so when one doesn't work, I trace down the reason, compose a entry in the 'live' fixincludes.def, and after I'm done with the 1000-or-so packages take all the bugs in one step back to the build directory and release them formally.
This would save lots of time - as it stands, the time to iterate through these issues is going to be very expensive. Ed On Tue, Oct 21, 2008 at 12:13 PM, Eric Botcazou <[EMAIL PROTECTED]> wrote: >> Is there any way to do this work with an already installed compiler, >> ie: change the fixincludes.def on the fly and have the installed >> compiler immediately pick up on the changes from the text file? > > You need to work in a build tree, modify fixincludes.def and follow the > instructions given in section 5. Testing fixes (which may or may not work > with the new toplevel bootstrap). Then do 'make install' in the dir. > > -- > Eric Botcazou >
