https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69757
--- Comment #6 from Edd Barrett <edd at theunixzoo dot co.uk> --- Ah hold on. More information. If I build a gcc with --disable-bootstrap, the resulting compiler cannot build an empty C program even: % /home/vext01/research/warmup_experiment/work/gcc-inst/bin/zgcc /tmp/a.c /usr/bin/ld: /tmp//ccGIx4CB.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /tmp//ccGIx4CB.o: could not read symbols: Bad value collect2: error: ld returned 1 exit status If I add -fPIC, the program compiles, but I do no expect to have to tack on -fPIC for such a program. This is probably why the second stage gcc build is failing too. I don't think we should have to pass down -fPIC to the second stage, no? Thanks
