https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86535
--- Comment #38 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #37 from Ian Lance Taylor <ian at airs dot com> --- > Search for this comment in the top-level configure.ac file. > > # Disable libgo for some systems where it is known to not work. > # For testing, you can easily override this with --enable-libgo. Ah, I'd missed that, being more used to the various lib*/configure.tgt files. The disadvantage of having this in the toplevel configure.ac is that this file is shared with binutils-gdb. > That said if you don't configure with --enable-languages=go then you shouldn't > get libgo. True. However, I did configure with --enable-languages=all (which expanded to c,ada,c++,d,fortran,go,lto,m2,objc,obj-c++,rust). Unfortunately, we lack a --disable-languages=<list>, so you need to use --enable-languages=<all of the above except go>, which is guaranteed to break (or rather miss new languages) as has happened to me for m2 and rust. It's best if GCC self-defends against configurations which are known not to work instead of having developers run into the trap first ;-)
