Re: [RFC] Go (golang) packaging

2013-01-02 Thread shawnlandden


Michael Stapelberg stapelb...@debian.org wrote:

Hi Matthias,

Matthias Klose d...@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.


-- 
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/800ddf68-acaf-4189-b5fe-674386639...@email.android.com



Re: [RFC] Go (golang) packaging

2013-01-02 Thread shawnlandden


Michael Stapelberg stapelb...@debian.org wrote:

Hi Shawn,

shawnland...@gmail.com writes:
 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.
If by “this binary” you mean godebiancontrol.a, then no:

ldd /tmp/golang/pkg/linux_amd64/github.com/mstap/godebiancontrol.a
   not a dynamic executable
.a files are just archives ( ar(1) i believe) of a bunch of .o files. They are 
not linked at all, either dynamically or statically. As gccgo uses libc6 and 
libgo1 and does not compile those every time you use it, you need libc6-dev and 
go Dev files to make any use of these .a files. You have to look at the 
resulting binaries.

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.


-- 
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/151dbbd0-ce6e-4289-8e27-21e8dbd03...@email.android.com