[Slackbuilds-users] Which "go" to use?
chris.willing at iinet.net.au
Wed Jun 22 02:53:30 UTC 2016
I built version from SBo master and since the resulting files didn't
seem to clash with /usr/bin/go from gcc-go, I installed the package
normally (into /). It all went well - I can now compile the go based
project I was having problems with.
On 22/06/16 01:13, Vincent Batts wrote:
> the gcc-go implementation, while largely OK, is known to have more
> edge-cases that are not supported. The nice thing is that the gcc-go
> that is provided by gcc v5+ is useful for _compiling_ the golang.org
> compiler (as the compiler itself is now written in golang).
> If you're running -current (soon to be 14.2), then check out
> which is updated for latest upstream stable.
> On Tue, Jun 21, 2016 at 8:20 AM, Ruben Schuller <mail at rbn.im> wrote:
>> On 2016-06-21 13:58, Christoph Willing wrote:
>>> I see we have a development/google-go-lang SlackBuild. However we
>>> already have /usr/bin/go from the stock gcc-go package.
>>> Does anyone have insights as to which is the preferred one to use?
>> They are different implementations of the Go language. I'd say the
>> golang.org (google) version is more widely used than the gcc version (which
>> I've never used).
>> My two cents:
>> From my own experience I'd recommend to just install the golang.org version
>> to somewhere in your $HOME and setting PATH accordingly. Either use a
>> precompiled version (https://golang.org/doc/install) or install from source
>> (https://golang.org/doc/install/source), both options are easy :)
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
More information about the SlackBuilds-users