2 suggestions

[Kaveh R. Ghazi]

 > > CONFIG_SHELL to /bin/ksh before configure;make bootstrap, they
 > > wouldn't have such insane build times.  I bet it cuts the 48 hours
 > > to single digits.
 > 
 > The trouble is that *people* are building this.  Googling turns up:
 > "Freemans rule: Nothing is so simple that it cannot be misunderstood"
 > 
 > So, I'd like to know if the variations in how to build GCC are so
 > numerous that having a collection of example build scripts is a stupid
 > idea.

I don't know about the utility of example scripts in general, but for
this specific case, I strongly feel autoconf should automatically
detect this and reexec the configure script under /bin/ksh.

If we follow "Freeman's Rule" then even the example script can be
misunderstood and having autoconf find ksh for you and run it behind
the scenes would be safer IMHO.

E.g. stick something like this near the top of every configure.ac in
the gcc tree:

	if test -z "$REEXECED" ; then
	  if test -z "$CONFIG_SHELL" ; then
	      CONFIG_SHELL=/bin/ksh ; export CONFIG_SHELL
	  fi
	  REEXECED=1 ; export REEXECED
	  exec $CONFIG_SHELL $0 $@
	fi

It's untested so you may need to tweek it.  But it conveys my idea.

		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu