https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98225
--- Comment #9 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #8 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot > Uni-Bielefeld.DE> --- >> The arguments are in a response-file: @outputs.ld1_args >> maybe that looks different for you? > > It certainly does (Solaris ld doesn't support -v, so no -Wl,-v here), as > I found in collect2.c (do_link): the @ files are only passed if > HAVE_GNU_LD and at_file_supplied. The former is certainly false for > Solaris ld, so we'll certainly see no outputs.ld1_args passed. I've now dug a bit further and found two things: In addition to the previous bootstraps with Solaris ld, I've run another one with GNU ld. As expected, the outputs.ld1_args FAILs are gone since, unlike Solaris ld, GNU ld *does* support response files. On a hunch, I've also run $ make -j2 check-gcc RUNTESTFLAGS=outputs.exp (with gld in use, but this doesn't make a difference as I mentioned) and lo, the previous FAILs now show up that didn't in a sequential make check-gcc.
