------- Comment #20 from skunk at iskunk dot org 2006-08-07 05:51 -------
(In reply to comment #19)
> Everything is always doable if resources permit. Tweaking CFLAGS is simply
> not generically supported and I don't think we have plan to that effect.
Okay. No generic flag-tweaking support is perfectly fine. Can we either...
(1) Straighten things out so that if you do have to pass a flag(s) to the
compiler, it is passed in through CFLAGS---thus respecting standard
flag-variable convention, or
(2) Ignore CFLAGS altogether, so that libiberty isn't built with it, and CC
becomes the only place where flags can be put in? (The thinking being, if the
behavior's going to be broken, at least make it _consistently_ broken)
> Simply use the documented procedure.
This isn't just about sparc64, you know. The whole reason why this came up in
the first place is because I'm building GCC in a custom autobuild framework,
across a number of architectures. For every other autotoolized package, I set
CC, CXX, {CC,CXX,CPP}FLAGS, and everything works. It's really annoying to have
GCC, a pretty important package, so thoroughly flout the convention that all
the other GNU toolsets adhere to.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28515
