[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 24 Apr 2013 15:55:25 +0200
From: Daniel Cegiełka <daniel.cegielka@...il.com>
To: musl@...ts.openwall.com
Subject: Re: Best place to discuss other lightweight libraries?
2013/4/24 Rich Felker <dalias@...ifal.cx>:
> On Wed, Apr 24, 2013 at 02:32:21PM +0200, Daniel Cegiełka wrote:
>> 2013/4/24 Kurt H Maier <khm-lists@...ma.in>:
>> > On Wed, Apr 24, 2013 at 01:18:43PM +0200, Daniel Cegiełka wrote:
>> >>
>> >> btw. has anyone used go with musl?
>> >>
>> >
>> > Go ships its own libc, which I'm fairly certain it depends on.
>>
>> lib9, but are you sure about that?
>>
>> # ldd /usr/bin/go
>> linux-vdso.so.1 => (0x00007fff50fff000)
>> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007ff215e4b000)
>> libc.so.6 => /lib64/libc.so.6 (0x00007ff215abf000)
>> /lib64/ld-linux-x86-64.so.2 (0x00007ff216068000)
>
> Is the go binary written in go?
Good question! :) If so, it should be statically linked.
http://code.google.com/p/go/source/browse#hg%2Fsrc%2Fcmd%2Fgo
> The point was that go links programs
> against its own libc, not that the go compiler is linked against its
> own libc.
I'm not sure if they really use __only__ their own libc (lib9). In my
opinion lib9 seems to refer to libc.
Daniel
> Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
