On Sun, 18 Dec 2011, Eric Botcazou wrote:
>> Here g++ is invoked without an absolute path, so if you have an older
>> version of g++ in your path that does not grok -Wno-narrowing yet that
>> will fail, won't it? I assume that's why only some like you and me are
>> seeing this, but not all of us.
> Yes, for some reason the base C++ compiler is used instead of the stage1 one.
So, the patch causing this was reverted and bootstrap worked again(?),
and now it is broken again with the same failure mode:
cc1: error: unrecognized command line option "-Wno-narrowing"
Actually, not the same, now it is invoking system gcc instead of
system g++:
gcc -I/scratch/tmp/gerald/gcc-HEAD/libcpp -I.
-I/scratch/tmp/gerald/gcc-HEAD/libcpp/../include -I./../intl
-I/scratch/tmp/gerald/gcc-HEAD/libcpp/include -g -f keep-inline-functions -W
-Wall -Wno-narrowing -Wwrite-strings -Wmissing-format-attribute
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wc++-compat
-pedantic -Wno-long-long -I/scratch/tmp/gerald/gcc-HEAD/libcpp -I.
-I/scratch/tmp/gerald/gcc-HEAD/libcpp/../include -I./../intl
-I/scratch/tmp/gerald/gcc-HEAD/libcpp/include -c -o identifiers.o -MT
identifiers.o -MMD -MP -MF .deps/identifiers.Tpo
/scratch/tmp/gerald/gcc-HEAD/libcpp/identifiers.c
And it happens in stage1 (stage1-bubble).
Gerald
