------- Comment #11 from skunk at iskunk dot org 2006-08-06 08:09 -------
(In reply to comment #9)
> You do for GCC. Tweaking CFLAGS for a bootstrap is a recipe for disaster.
How is it any worse than having those flags in CC? CC and CFLAGS are always
supposed to be used together anyway---the only difference with what you're
describing is that this follows the standard variable convention. (And surely
you're not implying that CFLAGS is supposed to be passed to xgcc or some other
stage, instead of BOOT_CFLAGS or similar?)
To say nothing of the issue of consistency: If CFLAGS is so bad, why is
libiberty built using it?
I understand that things are necessarily complicated in GCC's build system,
that you can have up to three (four?) different compilers and associated
options, etc. etc. No problem with that. What I don't understand is why, in the
simplest ("degenerate") case of bootstrapping a compiler on the target system,
I can't just blithely set CC+CFLAGS and have it work in the expected way.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28515
