Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 14 Mar 2014 17:09:06 +0100
From: Luca Barbato <>
Subject: Re: Static linking of musl with code compiled using GNU header

On 14/03/14 16:47, David Grothe wrote:
> I really don't want to port my code base to using the musl header
> files. 

There shouldn't be anything to port.

> I want to keep compiling with the GNU headers.  When I do this
> and link my-huge-program.o with musl libc.a I get the following list of
> unresolved externals:
>          U __divdi3
>          w __fini_array_end
>          w __fini_array_start
>          U __moddi3
>          U __sysv_signal
>          U __udivdi3
>          U __umoddi3

>          U __vfprintf_chk
>          U __vsnprintf_chk
>          U __vsprintf_chk

>          U __sysv_signal
> So, I am wondering if the musl library could at some point provide these
> routines to enable users to do what I am trying to do.

Not sure, but those internal symbols are close to implementation details...


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.