egcs-1.1.1 issues

[Bruce Korb]

Robert Lipe wrote:

> > Since I know the following [ related to fast fixincludes ] :

> [...]]

> Perhaps we should at least build a plan for the steps we take to enable
> this as the default.  Maybe we start by asking testers of the trunk to
> configure '--with-fast-fixincludes'.  Once that has had sufficient air
> time without problems we make it the default.  Then we proceed to remove
> (or at least mark as deprecated) the old stuff.  There may be pitstops
> along the way or other steps needed, but maybe a clear "TODO" list is in
> order.
>
> Let's just figure out how to get this out of limbo so it can start
> helping users and developers.

I have already wired it so that by moving the fixinc.* files fromegcs/gcc to
egcs/contrib/fixinc and deleting egcs/gcc/fixincludes
you will have exactly the same result you have today.  From that point,
you can start removing the egcs/contrib/fixinc.??* files that got
moved in and removing the special entries in the egcs/contrib/mkfixinc.sh
file.  This would be done only as it is verified that either the
fixincl program or the inclhack.sh script produced correct results.
(The mkfixinc.sh script tries to build a working program and, if it fails,
then copies the massive inclhack.sh script into place.)


By the way, I *would* like to distribute autogen via anonymous
CVS off of egcs.cygnus.com.  That way, developers would be able
to do a "make" in the egcs/contrib/fixinc directory (assuming they
install the autogen binary).  Would it be best as egcs/contrib/autogen/...
or as straight up autogen/...*, a la guile?