| 1 |
On Tue, 3 Nov 2015 08:56:29 -0600 |
| 2 |
William Hubbs <williamh@g.o> wrote: |
| 3 |
|
| 4 |
> As has been pointed out in the thread so far, gcc-5 only supports |
| 5 |
> go-1.4. dev-lang/go is at 1.5, so really the only thing that should be |
| 6 |
> built with gccgo is dev-lang/go. Also, the golang eclasses are |
| 7 |
> designed to work with dev-lang/go, so they do not need a dependency |
| 8 |
> on gccgo. |
| 9 |
> |
| 10 |
> I see gcc-5[go] as a separate Go compiler, but it will always be |
| 11 |
> behind dev-lang/go, so you will have things that build with |
| 12 |
> dev-lang/go but not gccgo. Also, the commands to do the builds are |
| 13 |
> completely different depending on which one you are using. |
| 14 |
|
| 15 |
This is a lot like the situation with gcc's gcj and the icedtea Java |
| 16 |
JDK. The arguments are quite different so we have a wrapper script |
| 17 |
packaged as gcj-jdk. gcj only supports Java 6(ish?) and there are |
| 18 |
other compatibility issues though so we no longer support it as a |
| 19 |
general purpose JDK. Its only use is for bootstrapping icedtea. Now |
| 20 |
that Java has been open sourced and gcj has fallen so far behind, gcc |
| 21 |
are planning to scrap it so icedtea will need to find another way to |
| 22 |
bootstrap (probably JamVM) if it isn't to rely on prebuilt versions of |
| 23 |
itself. |
| 24 |
|
| 25 |
-- |
| 26 |
James Le Cuirot (chewi) |
| 27 |
Gentoo Linux Developer |
Archives