https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114985
--- Comment #29 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- (In reply to r...@cebitec.uni-bielefeld.de from comment #28) > > --- Comment #27 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- > > This is in cfarm216.cfarm.et: > > > > aldyh@s11-sparc:~/bld/clean$ hostname > > s11-sparc.cfarm > > aldyh@s11-sparc:~/bld/clean$ uname -a > > SunOS s11-sparc.cfarm 5.11 11.4.68.164.2 sun4v sparc sun4v logical-domain > > aldyh@s11-sparc:~/bld/clean$ ~/src/clean/configure && gmake -j80 && gmake > > check > > -k -j80 > > You need to be careful that the assembler and linker actually used match > gcc's idea thereof: > > https://gcc.gnu.org/install/specific.html#x-x-solaris2 > > Best specify all of --build sparcv9-sun-solaris2.11 (if you're > bootstrapping with a 64-bit-default gcc/g++) and > > --with-as=/usr/gnu/bin/as (or /opt/cfarm/binutils-latest-64/bin/as) > --with-gnu-as > > (/usr/bin/as works too, but you need to specify both the path and > --without-gnu-as) > > --with-ld=/usr/bin/ld > --without-gnu-ld > > Having two different assemblers and linkers (Solaris and GNU) available > can lead to confusion if you rely on PATH alone. Ok, what's the minimum configuration I need to build here? srcdir/configure --build=sparc-sun-solaris2.11 srcdir/configure --build=sparc-sun-solaris2.11 --without-gnu-as --without-gnu-ld ?? I really don't care how it builds, I just want the bare minimum so I can bootstrap and run tests. A minor rant, but why can't all this be set up automatically in the compile farm machines? Keeping track of minor nuances of each architecture is distracting. They should all be set up, whether by setting default paths in /etc/profile or whatever, or by having the relevant patches in GCC's source base, such that they work with src/configure && make. I know this isn't your fault, but if more cfarm boxes where set up to go with no surprises, I'd add more boxen to my testing harness. > > > gmake[3]: Leaving directory '/home/aldyh/bld/clean' > > Comparing stages 2 and 3 > > Bootstrap comparison failure! > > gcc/tree-vect-stmts.o differs > > I'm not seeing this myself. Dunno. It could be the particular revision was broken??
