On Fri, 27 Sep 2013, Tom Tromey wrote: > Look a little further down in the patch: > > .cc.o .c.o: > - $(COMPILER) -c $(ALL_COMPILERFLAGS) $(ALL_CPPFLAGS) $< $(OUTPUT_OPTION) > + $(COMPILE) $< > + $(POSTCOMPILE) > > ... that is, the patches didn't change this part. ALL_COMPILERFLAGS was > used before and it is used now. I don't think this series touched how > this variable is computed, either.
Looks like this was a red herring. Sorry for that. > If I were debugging this then I think I would start by looking in > config.log to see why the compiler accepted -Wno-narrowing. On Mon, 30 Sep 2013, Paolo Bonzini wrote: > Why is install building anything? I believe this may be the key element. Configury really is _not_ an area I am an expert in, but I did some experiments: - Revision r202892 | law | 2013-09-25 15:33:34 +0000 (Wed, 25 Sep 2013) builds just fine on my tester(s). Revision r202912 | tromey | 2013-09-25 16:33:30 +0000 (Wed, 25 Sep 2013) fails. So, this definitely was introduced by this patch set. - When I do a gmake at the top level of the build tree, nothing is rebuilt at all. This only happens during `gmake install` - The problem is not actually the set of flags being used. On a different tester clang is the bootstrap compiler, and this is also the one invoked for `gmake install`. If anything, shouldn't the just built compiler be used _if_ anything is left to compile? Is nobody else seeing this? Or is everyone just lucky enough to have a recent version of GCC as the default compiler? Gerald
