Am 02.01.2013 03:54, schrieb Paul Wise: > On Wed, Jan 2, 2013 at 12:14 AM, Michael Stapelberg wrote: > >> Only when not using the “official” compiler (gc), e.g. gccgo has support >> for dynamic linking. > > Then we should use gccgo until the official compiler supports this. > >> AFAIK not, but I will add this to the list of questions I want to ask on >> the Go mailing lists. > > Ok, please let us know about the results.
Calling gc the "official" compiler seems to be misleading. gccgo in wheezy supports the Go API 1.0, and the standard library 1.0.3, supports dynamic linking, supports multiarch, makes the distinction for armel/armhf, and supports cross-compilation. I don't mind having a second compiler in the archives like clang, but please make sure that you are not bound to one. How does your packaging proposal work with gccgo as the compiler? Did you consider making gc an alternative (like cc, c++)? Matthias -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50e4418e.3040...@debian.org
