testing consistency
Alexandre Oliva
oliva@dcc.unicamp.br
Mon Sep 15 14:44:00 GMT 1997
> The first step in this process is to get everyone to bootstrap in the
> same manner. Is anyone else using the rough toplevel "bootstrap"
> target I posted last week? Comments and improvements are definitely
> welcome!
I'm not using that bootstrap yet because it lacks some features I
really need:
1) the ability to specify additional flags to be used to build gcc. I
currently have to append a strtoul-related flag to CFLAGS and
BOOT_CFLAGS so that I can build g77 on SunOS 4.1.3, and I can only do
that by using the bootstrap target in the gcc directory.
2) the ability to continue a build from a given stage on, as I can do
with bootstrap2 & bootstrap3.
Also, I don't think bootstrap should make compare. Maybe I'm just
used to the ol' gcc bootstrap behavior, but I don't think building gcc
has anything to do with comparing it. Maybe make check should do
it...
Here's a patch that provides bootstrap[23] targets, and removes the
BOOT_CFLAGS from the make invocation. Doing this, BOOT_CFLAGS may be
overridden, and, if it is not, the default BOOT_CFLAGS from the gcc
Makefile will be used.
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
Universidade Estadual de Campinas, SP, Brasil
More information about the Gcc
mailing list