On Fri, May 22, 2015 at 2:01 PM, Andrew Chambers <andrewchambe...@gmail.com> wrote: >> >> For example, I've tested on an x86, built cross compilers for ppc64 and >> ppc64le and then can invoke the native go tool (built to run on x86) to >> compile with either target compiler by changing my GOARCH value. I don't >> want to have a separate cross go tool to use only for ppc64 and another to >> use only for ppc64le. > > > If I have mips-linux-gcc , mips-linux-gccgo, there is no reason to not have > a mips-linux-go which automatically uses the correct gccgo and is installed > into the same prefix. > It is in line with how gcc works currently, Also, for a canadian cross > compile (--build differs to --host), building a new go tool is necessary > anyway.
With the gc toolchain, it's very convenient to be able to say GOARCH=arm go build program to get the ARM version of a program. I don't think we should move away from that in order to follow GCC conventions. The Go conventions are better and easier to use. Ian
