Fixes go 1.1.2 compilation on OSX Maverick

[zimbatm]

Apparently Apple thinks that faking gcc wiht a clang stub but not providing a
compatile libgcc.a is not going to cause any issues. They really do hate GPL.

[viric]

On Sun, Nov 17, 2013 at 05:35:57AM -0800, Jonas Pfenniger wrote:

Apparently Apple thinks that faking gcc wiht a clang stub but not providing a
compatile libgcc.a is not going to cause any issues. They really do hate GPL.

So it is a broad apple issue? Isn't this patch harming any users then? Other
versions of the OS, ...

[zimbatm]

It's true that not everyone is affected and that disabling gccgo prevent from some go programs to compile (those who rely on external C libraries).

There are two bugs introduced by Xcode 5's compiler tool-chain. One where libgcc.a is missing and one where clang is outputting some broken code, both affecting gccgo. The go team is aware of the issues and will have a fix available for go 1.1.3. For the details see http://code.google.com/p/go/issues/detail?id=5926

[bluescreen303]

Please make this optional, I use cgo functionality and don't want to be
crippled by apple. If I would have liked that, I would have bought a mac.

On Sun, Nov 17, 2013 at 10:52 PM, zimbatm notifications@github.com wrote:

It's true that not everyone is affected and that disabling gccgo prevent
from some go programs to compile (those who rely on external C libraries).

There are two bugs introduced by Xcode 5's compiler tool-chain. One where
libgcc.a is missing and one where clang is outputting some broken code,
both affecting gccgo. The go team is aware of the issues and will have a
fix available for go 1.1.3. For the details see
http://code.google.com/p/go/issues/detail?id=5926

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/1231#issuecomment-28665122
.

[zimbatm]

Are you using another Darwin derivative ? If you're using Linux then 1.1.nix is unaffected by that change.

[bluescreen303]

ah, sorry in that case :) I didn't see there was a separate 1.1-darwin
derivation.
This is actually better than spraying every derivation with lots of
optional darwin flags and tricks.

On Sun, Nov 17, 2013 at 11:11 PM, zimbatm notifications@github.com wrote:

Are you using another Darwin derivative ? If you're using Linux then
1.1.nix is unaffected by that change.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/1231#issuecomment-28665602
.