On Sat, 2014-08-16 16:22:13 +0200, Manuel López-Ibáñez <lopeziba...@gmail.com> wrote: > Could you explain a bit the setup of the buildbot? > > >From the logs, it is not evident that it is bootstrapping the > compiler, and the first stage compiler should not be using -Werror. If > not that, there must be some difference between the buildbot setup and > the default setup in x86_64-gnu-linux because I have boostrapped this > patch before and after committing the changes.
This build took place on gcc20.fsffrance.org, using GCC's
./contrib/config-list.mk .
Instead of letting config-list.mk build all target at once, it's
invoked with a log filename so that it only builds a single target; so
this specifically boils down to:
mkdir log
make -f ../gcc/contrib/config-list.mk "log/i686-apple-darwin-make.out"
(...or any other target.) So if there's something wrong with how
config-list.mk builds:
$(LIST): make-log-dir
-mkdir $@
(cd $@ && \
../../gcc/configure \
--target=$(subst SCRIPTS,`pwd`/../scripts/,$(subst OPT,$(empty) -,$@)) \
--enable-werror-always ${host_options} --enable-languages=all,ada,go) \
> log/$@-config.out 2>&1
There's --enable-werror-always, though that didn't trigger before (et
least not for the printf'ish checks.) So what's specifically different
with this new function?
Mfe, JBG
--
Jan-Benedict Glaw jbg...@lug-owl.de +49-172-7608481
Signature of: The course of history shows that as a government grows, liberty
the second : decreases." (Thomas Jefferson)
signature.asc
Description: Digital signature
