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)


On Apr 12, 2001, Franz Sirl <Franz.Sirl-kernel@lauterbach.com> wrote:

> -BOOT_CFLAGS = -g -O2
> +CFLAGS = -g
>  STAGE1_CFLAGS = -g @stage1_cflags@
> -CFLAGS = $(STAGE1_CFLAGS)
> +BOOT_CFLAGS = -g $(CFLAGS)

Here's something I don't understand.  Why is BOOT_CFLAGS forced to
start with `-g'?  IMO, it should be exactly $(CFLAGS).  Thinking of
the perspective of someone who ones CFLAGS, as passed to make, to
affect the compilation of the final executables, I'd expect CFLAGS to
be used to build stage3 of the bootstrap (and stage2, so that compare
passes).  So, I'd just let CFLAGS be AC_SUBSTed, and default
BOOT_CFLAGS to $(CFLAGS).  It is STAGE1_CFLAGS that should be handled
differently.
 
-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me


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