This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] gcc/Makefile.in gcc-3_0-branch, pass CFLAGS to stage1_build
- To: Richard dot Earnshaw at arm dot com
- Subject: Re: [PATCH] gcc/Makefile.in gcc-3_0-branch, pass CFLAGS to stage1_build
- From: DJ Delorie <dj at redhat dot com>
- Date: Mon, 26 Mar 2001 14:15:00 -0500
- CC: gcc-patches at gcc dot gnu dot org, gbsadler1 at lcisp dot com
- References: <200103261635.RAA16247@cam-mail2.cambridge.arm.com>
> Can we back out the following please? There's no technical need for it,
> and the only effect is that it shaves a small amount of time of the stage2
> build.
If we back it out, there is *no* way to override stage1 compile flags,
and it will use the CFLAGS inherent in the Makefile (which is no
different that what the Makefile does now, if you don't specify
CFLAGS= on the "make" command line - it defaults to STAGE1_CFLAGS
already). I'm sure this isn't what you want.
The current stage1_build command looks like this:
$(MAKE) CC="$(CC)" libdir=$(libdir) LANGUAGES="$(BOOT_LANGUAGES)" \
CFLAGS="$(CFLAGS)"
Any variables not listed in this command will assume the default
values encoded inside the Makefile. These defaults are supposed to be
set as if the compiler is the installed compiler. If you can't build
with the installed compiler without passing flags, you won't be able
to bootstrap with that compiler without passing the same flags, and
those flags need to be listed like the CFLAGS example above.