Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-12-21 Thread William Hubbs
All, was this patch ever applied to gcc? If so, which versions? Thanks, William signature.asc Description: Digital signature

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-04 Thread William Hubbs
On Tue, Nov 03, 2015 at 03:09:52PM +, James Le Cuirot wrote: > On Tue, 3 Nov 2015 08:56:29 -0600 > William Hubbs wrote: > > > As has been pointed out in the thread so far, gcc-5 only supports > > go-1.4. dev-lang/go is at 1.5, so really the only thing that should be > >

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-03 Thread James Le Cuirot
On Tue, 3 Nov 2015 08:56:29 -0600 William Hubbs wrote: > As has been pointed out in the thread so far, gcc-5 only supports > go-1.4. dev-lang/go is at 1.5, so really the only thing that should be > built with gccgo is dev-lang/go. Also, the golang eclasses are > designed to

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-03 Thread Zac Medico
On 11/02/2015 09:17 AM, Leno Hou wrote: > -DEPEND=">=dev-lang/go-1.4:= > +DEPEND="|| ( > + >=dev-lang/go-1.4:= > + >=sys-devel/gcc-5.1.0:=[go] > + ) Note that the council has recently decided that the := operator is explicitly forbidden inside || ( ) constructs. The

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-03 Thread Leno Hou
On Tue, Nov 3, 2015 at 3:45 PM, Justin (jlec) wrote: > On 02/11/15 23:38, William Hubbs wrote: > Hi William, > > but instead of adding > > DEPEND="||ยท( > >=dev-lang/go-1.4 > >=sys-devel/gcc-5.1.0:=[go] > > to ebuilds, you could create a virtual/go with that

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-03 Thread William Hubbs
On Tue, Nov 03, 2015 at 08:45:00AM +0100, Justin (jlec) wrote: > On 02/11/15 23:38, William Hubbs wrote: > > On Mon, Nov 02, 2015 at 09:12:30PM +0100, Justin Lecher (jlec) wrote: > >> -BEGIN PGP SIGNED MESSAGE- > >> Hash: SHA512 > >> > >> How about a virtual here? > > > > I don't see that

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-02 Thread Justin (jlec)
On 02/11/15 23:38, William Hubbs wrote: > On Mon, Nov 02, 2015 at 09:12:30PM +0100, Justin Lecher (jlec) wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA512 >> >> How about a virtual here? > > I don't see that working out to well because the compilers are > completely different from each

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-02 Thread Justin Lecher (jlec)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 How about a virtual here? -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0 iQJ8BAEBCgBmBQJWN8OuXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0QUU0N0I4NzFERUI0MTJFN0EyODE0NUFF

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-02 Thread William Hubbs
On Mon, Nov 02, 2015 at 12:17:26PM -0500, Leno Hou wrote: > 1. go compiler only support x86 platform > 2. gcc 5 includes go command to build go apps > 3. for coreos enablement, it's use gcc 5 to build go apps Also, once this is in place, I believe I could use gccgo to build go-1.5 and newer,

[gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-02 Thread Leno Hou
1. go compiler only support x86 platform 2. gcc 5 includes go command to build go apps 3. for coreos enablement, it's use gcc 5 to build go apps Signed-off-by: Leno Hou --- app-admin/consul-template/consul-template-0.9.0-r1.ebuild | 5 -

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-02 Thread William Hubbs
On Mon, Nov 02, 2015 at 09:12:30PM +0100, Justin Lecher (jlec) wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > How about a virtual here? I don't see that working out to well because the compilers are completely different from each other. As I said, the reference implementation of

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-02 Thread Leno Hou
On Tue, Nov 3, 2015 at 6:38 AM, William Hubbs wrote: > On Mon, Nov 02, 2015 at 09:12:30PM +0100, Justin Lecher (jlec) wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > How about a virtual here? > > I don't see that working out to well because the