Re: [RFC] Go (golang) packaging

[shawnlandden@gmail.com]

Michael Stapelberg <stapelberg@debian.org> wrote:

>Hi Matthias,
>
>Matthias Klose <doko@debian.org> writes:
>> Calling gc the "official" compiler seems to be misleading. gccgo in
>That’s why I called it “official”, not official.
>
>> 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++)?
>I am trying to evaluate how this would work. Here is what I tried:
>
>/tmp/golang/pkg/linux_amd64/github.com/mstap:
>total 36K
>-rw-r--r-- 1 michael staff 34K 2013-01-02 15:59 godebiancontrol.a
>
>Now, obviously this is not dynamically linked. Neither does it use
>different host triplets.
>
>How do I make gccgo use dynamic linking?

I am not sure how or if lld works on .a files, but I am pretty sure that this binary is linked against libc6 and libgo1. If I invoke gccgo directly that is the result.
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.