This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/28515] CFLAGS not propagated, resulting in object mismatch
- From: "skunk at iskunk dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Jul 2006 02:20:03 -0000
- Subject: [Bug bootstrap/28515] CFLAGS not propagated, resulting in object mismatch
- References: <bug-28515-8784@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from skunk at iskunk dot org 2006-07-28 02:20 -------
(In reply to comment #3)
>
> make STAGE1_CFLAGS=whatever
Yes. Editing the makefile works pretty well too :-)
But the point is, it's a bug for cc(1) to have been invoked without the
original CFLAGS. I admit that I don't fully understand how the
host/system/build/stageN settings are partitioned, but it seems like a pretty
clear problem for a straight-up CC+CFLAGS environment to give the build error I
quoted. Methinks something like
STAGE1_CFLAGS=${STAGE1_CFLAGS-${CFLAGS}}
should be happening at configure time, that STAGE1_CFLAGS can be set if you
want GCC's stage 1 to be built with different flags than libiberty, but
otherwise that you can just set CC+CFLAGS as usual and have it all work.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28515