Tom Browder <tom.browder@xxxxxxxxx> writes: > I just had it happen: > > $ cd gcc_build > $ make distclean > $ ls -aCF > ./ ../ fixincludes/ stage_final > $ ../gcc-5.5.1/configure > $ make pdf > make[1]: Entering directory `/usr/local/src/gcc_build' > make[2]: Entering directory `/usr/local/src/gcc_build' > make[2]: Leaving directory `/usr/local/src/gcc_build' > Configuring in ./fixincludes > configure: loading cache ./config.cache > configure: error: `CC' has changed since the previous run: > configure: former value: `/usr/local/src/gcc_build/./gcc/xgcc > -B/usr/local/src/gcc_build/./gcc/ > -B/usr/local/x86_64-unknown-linux-gnu/bin/ > -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem > /usr/local/x86_64-unknown-linux-gnu/include -isystem > /usr/local/x86_64-unknown-linux-gnu/sys-include ' > configure: current value: `gcc-4.5.1' > configure: error: in `/usr/local/src/gcc_build/fixincludes': > configure: error: changes in the environment can compromise the build > configure: error: run `make distclean' and/or `rm ./config.cache' and start over > make[1]: *** [configure-fixincludes] Error 1 > make[1]: Leaving directory `/usr/local/src/gcc_build' > make: *** [do-pdf] Error 2 > > So, Ian, a bug report shall I submit? Sure. There is presumably a fixincludes/config.cache file, which should have been removed by "make distclean". Thanks. Ian
