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: dave at hiauly1 dot hia dot nrc dot ca
- Subject: Re: [PATCH] gcc/Makefile.in gcc-3_0-branch, pass CFLAGS to stage1_build
- From: DJ Delorie <dj at redhat dot com>
- Date: Tue, 27 Mar 2001 15:21:11 -0500
- CC: gcc-patches at gcc dot gnu dot org, Franz dot irl-kernel at lauterbach dot com
- References: <200103272009.PAA11093@hiauly1.hia.nrc.ca>
> The currently installed patch is wrong and should be backed out.
I'd rather fix it than return to the previous state, which was also
wrong.
> For native builds, it is necessary to have different CFLAGS for
> stage1 and subsequent stages on some hosts. The stage1 compile
> flags are the default values set in the Makefile. These currently
> are set by configure and not directly passed to the stage1 build.
> Passing STAGE1_CFLAGS from the toplevel Makefile would apprear to
> provide a method to override the defaults set by configure.
So let's fix it to use stage1_cflags, yes? Then we can pass
STAGE1_CFLAGS from the toplevel Makefile.
Index: Makefile.in
===================================================================
RCS file: /cvs/gcc/gcc/gcc/Makefile.in,v
retrieving revision 1.629
diff -p -3 -r1.629 Makefile.in
*** Makefile.in 2001/03/22 21:48:15 1.629
--- Makefile.in 2001/03/27 20:19:41
*************** STAGE2_FLAGS_TO_PASS = \
*** 2925,2931 ****
# only thing useful for building stage2.
stage1_build:
$(MAKE) CC="$(CC)" libdir=$(libdir) LANGUAGES="$(BOOT_LANGUAGES)" \
! CFLAGS="$(CFLAGS)"
touch stage1_build
echo stage1_build > stage_last
--- 2925,2931 ----
# only thing useful for building stage2.
stage1_build:
$(MAKE) CC="$(CC)" libdir=$(libdir) LANGUAGES="$(BOOT_LANGUAGES)" \
! CFLAGS="$(STAGE1_CFLAGS)"
touch stage1_build
echo stage1_build > stage_last