On Mon, Oct 27, 2014 at 8:06 AM, Jan-Benedict Glaw <jbg...@lug-owl.de> wrote: > > On Wed, 2014-10-22 20:36:53 -0700, Ian Taylor <i...@golang.org> wrote: >> This patch to the top level GCC configure script disables the go >> languages on some systems where it is known to not work. Bootstrapped >> on x86_64-unknown-gnu-linux. > > I don't have a clue here, but in what way is Go broken for these > targets? Bacause this patch "breaks" a number of targets mentioned in > contrib/config-list.mk. Maybe Go didn't work on these, but it at > least built. Is it FUBAR there? Or just little fixes needed?
I'm not sure exactly what you mean by "breaks," here, as Go is never in the set of default languages. It should only break builds that are using --enable-languages=go. And for those targets, the Go support has never worked, so they were already broken. For Darwin I expect that only small fixes are needed. This is http://gcc.gnu.org/PR46986. For Windows the compiler probably only needs small fixes, but the libgo build will need a bunch of support, particularly in the syscall package. The support for Windows is mostly there in the code, because it is in the master Go library, but it's not being built for libgo. For AIX I'm not sure. It's probably not too much work. Ian
