Re: Patch RFA: Support for building Go tools

2015-01-15 Thread Ian Lance Taylor
On Wed, Jan 14, 2015 at 11:07 AM, Uros Bizjak wrote: > >> This patch adds support to the GCC tree for building tools that are >> used with Go. There are two external used tools (go, gofmt) and one >> tool used internally by go (cgo). This patch is pure machinery, with >> no source code. The too

Re: Patch RFA: Support for building Go tools

2015-01-14 Thread Uros Bizjak
Hello! > This patch adds support to the GCC tree for building tools that are > used with Go. There are two external used tools (go, gofmt) and one > tool used internally by go (cgo). This patch is pure machinery, with > no source code. The tools are not built by default, only when go is > enabl

Re: Patch RFA: Support for building Go tools

2015-01-09 Thread Ian Lance Taylor
Committed initial gotools patch with following ChangeLog entries: ./: 2015-01-09 Ian Lance Taylor * configure.ac (host_tools): Add gotools. * Makefile.def (host_modules): Add gotools. (dependencies): Add dependency of all-gotools on all-target-libgo. gcc/go/: 2015-01

Re: Patch RFA: Support for building Go tools

2015-01-09 Thread Ian Lance Taylor
On Fri, Jan 9, 2015 at 7:40 AM, Paolo Bonzini 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 ver

Re: Patch RFA: Support for building Go tools

2015-01-09 Thread Paolo Bonzini
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

Re: Patch RFA: Support for building Go tools

2015-01-09 Thread Ian Lance Taylor
On Fri, Jan 9, 2015 at 12:54 AM, Paolo Bonzini wrote: > >> + >> +# For a non-native build we have to build the programs using a >> +# previously built host (or build -> host) Go compiler. We should >> +# only do this if such a compiler is available. Figure this out >> +# later. >> + >> +endif >

Re: Patch RFA: Support for building Go tools

2015-01-09 Thread Paolo Bonzini
On 08/01/2015 22:35, Ian Lance Taylor wrote: > > +if NATIVE > + > +# For a native build we build the programs using the newly built libgo > +# and install them as regular programs. > + > +bin_PROGRAMS = go$(EXEEXT) gofmt$(EXEEXT) > +libexecsub_PROGRAMS = cgo$(EXEEXT) > + > +go$(EXEEXT): $(go_cmd

Re: Patch RFA: Support for building Go tools

2015-01-08 Thread pinskia
> On Jan 8, 2015, at 1:35 PM, Ian Lance Taylor wrote: > > This patch adds support to the GCC tree for building tools that are > used with Go. There are two external used tools (go, gofmt) and one > tool used internally by go (cgo). This patch is pure machinery, with > no source code. The t

Patch RFA: Support for building Go tools

2015-01-08 Thread Ian Lance Taylor
This patch adds support to the GCC tree for building tools that are used with Go. There are two external used tools (go, gofmt) and one tool used internally by go (cgo). This patch is pure machinery, with no source code. The tools are not built by default, only when go is enabled using --enable-