You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried building via the procedure documented at https://golang.org/doc/install/gccgo using the gccgo branch. Hit a problem during configure. iant on the IRC informs me that Darwin is currently not supported. Not a blocker, but based on https://sourceware.org/gdb/wiki/GoDebugging the gccgo debugger support is fairly close to complete, and intellij and/or emacs with debug support might be handy in a pinch.
Longer-term LLDB might be the destination so maybe this is moot.
That said, checking out the source takes a while and there are a lot of devs using Darwin. It might be nice if the gccgo page said, up-front, which platforms were currently supported. Ideally in a manner which pulled from the actual install metadata. The configure might also detect this ASAP. Just saying. When Mr. Kernighan's book is released there will be a wave of people looking into the new-and-improved 'c'.
The text was updated successfully, but these errors were encountered:
Tried building via the procedure documented at https://golang.org/doc/install/gccgo using the gccgo branch. Hit a problem during configure. iant on the IRC informs me that Darwin is currently not supported. Not a blocker, but based on https://sourceware.org/gdb/wiki/GoDebugging the gccgo debugger support is fairly close to complete, and intellij and/or emacs with debug support might be handy in a pinch.
Longer-term LLDB might be the destination so maybe this is moot.
That said, checking out the source takes a while and there are a lot of devs using Darwin. It might be nice if the gccgo page said, up-front, which platforms were currently supported. Ideally in a manner which pulled from the actual install metadata. The configure might also detect this ASAP. Just saying. When Mr. Kernighan's book is released there will be a wave of people looking into the new-and-improved 'c'.
The text was updated successfully, but these errors were encountered: