On Fri, Jan 9, 2015 at 7:40 AM, Paolo Bonzini <bonz...@gnu.org> wrote: > > > On 09/01/2015 15:24, Ian Lance Taylor wrote: >>> > >>> > This should work automatically, the only difference is that you must >>> > omit $(LIBGODEP) from the dependencies. >> What will happen if there is no installed gccgo at the right version? > > Compilation fails. > >> What should happen? > > Compilation fails. :) > >> I haven't been keeping track--will the build machinery now build a >> build-x-host Go compiler? > > No, but the build machinery should point the Makefile variables to a > build-x-host tool from the PATH. If it doesn't, you need to modify the > toplevel configure.ac and Makefile.tpl.
I forgot: there is another problem with using the build-x-host compiler to build the tools. That will build them with the host version of the go/build package, which will set the default values for the architecture and OS to be that of the host, not the target. They should really be the target. We can fix this, but it will require some thought. I plan to commit the version that does not do anything when building a cross-compiler in order to proceed. The situation will not be worse than it is today. Ian
