This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Mainline bootstrap failure (Re: libstdc++ execute tests)


At 22:56 12.04.2001, Alexandre Oliva wrote:
>On Apr 12, 2001, Franz Sirl <Franz.Sirl-kernel@lauterbach.com> wrote:
>
> > So it seems we just misunderstood each other, I thought you _wanted_
> > CFLAGS to override things like BOOT_CFLAGS for a bootstrap compile...
>
>Err...  I do want BOOT_CFLAGS = $(CFLAGS) by default.  And I want
>CFLAGS = -g -O2 by default.  And STAGE1_CFLAGS = -g by default.
>It's BOOT_CFLAGS that should be affected by the incoming CFLAGS, not
>STAGE1_CFLAGS.  IMHO :-)

Uhm, the default CFLAGS is never used with my patch during a bootstrap 
compile and for a cross compile it doesn't make sense to put a gcc specific 
opt flag in there.

STAGE1_CFLAGS has no relation to CFLAGS at all with my patch, so what's the 
point?

If we default BOOT_CFLAGS to CFLAGS we have exactly the situation Gaby and 
I don't want, namely that a "make bootstrap CFLAGS=<system-compilerflags>" 
in the toplevel will break with a non-gcc system compiler. If we want that, 
we need to break the connection between CFLAGS and CFLAGS_FOR_TARGET in the 
toplevel Makefile.in.

Franz.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]