🚀 go-pugleaf

Ok, so gcc 2.5.x is in a beating-out-the-bugs cycle and you typically
run a re-compile every other day. This is good for fixincludes, because
you pick up changed /usr/include stuff into the gcc-lib subtree each time.

Now say you have a box which doesn't get gcc rebuilt so frequently. Maybe
you install some kernel mods, maybe you just frob /usr/include.

gcc looses big because you will pick up un-fixincluded versions of header files
and remembering to check for this is not often easy.

Can some way be found to keep fixincludes automatic in gcc rebuild, but
unbundle it sufficiently that it can be installed as a distinct runnable task
and run outside of the normal compiler install sequence periodically?

-George
-- 
                         George Michaelson
G.Michaelson@cc.uq.oz.au The Prentice Centre      | A squid eating dough in a
                         University of Queensland | polyethylene bag is fast
Phone: +61 7 365 4079    QLD Australia 4072       | & bulbous  (Don Van Vliet)