From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Cc: Support at Gcom <support@Gcom.com>
Subject: Re: Static linking of musl with code compiled using GNU header files
Date: Fri, 14 Mar 2014 12:47:20 -0400 [thread overview]
Message-ID: <20140314164720.GG184@brightrain.aerifal.cx> (raw)
In-Reply-To: <53232493.80901@gcom.com>
On Fri, Mar 14, 2014 at 10:47:31AM -0500, David Grothe wrote:
> Hello,
>
> I have a very large code base that I have been compiling on Linux
> using the standard GNU C compiler [gcc (Ubuntu/Linaro
> 4.6.3-1ubuntu5) 4.6.3]. I have been using shared object libraries,
> but for reasons of software support I would now like to link all my
> commands (a couple of dozen) and daemons using static libraries so
> that the code files are self-contained and can be copied, along with
> a core file, to any server back in my shop for analysis. With
> dynamic libraries I have to have exactly the same version of libc
> installed on the machine that I use to examine the core file as were
> present on the machine that generated the core file, or else gdb
> will not produce a stack back trace with file and line number
> information. So much for the background.
>
> I really don't want to port my code base to using the musl header
> files. 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
The presence of __divdi3, __moddi3, __udivdi3, and __umoddi3 in this
list indicates that you're missing libgcc.a. If you're using
-nostdlib, you need to manually add libgcc back to the linker command
line. __fini_array_start and __fini_array_end are provided by the
linker and are not necessary unless your code has global destructors
that the compiler is implementing via fini_array (this is why they're
weak).
The rest are __sysv_signal and __*_chk. The former looks suspicious: I
really doubt you _want_ to be using the sysv version of signal(); it
probably got pulled in by glibc's headers due to bad feature test
macros or something. As for the latter, these come from
_FORTIFY_SOURCE which musl does not yet support.
> 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.
>
> Any possibility of that?
Likely for at least some of them, but not right away. And there are at
least a few features (e.g. pthread cancellation) that will never work
this way.
BTW is there a reason you want to use glibc's headers with musl? If
your program is having lots of build errors with musl's, it's probably
indicative of problems you should fix; some of these problems may
become problems with future glibc versions too.
Rich
prev parent reply other threads:[~2014-03-14 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 15:47 David Grothe
2014-03-14 16:09 ` Luca Barbato
2014-03-14 16:29 ` Szabolcs Nagy
2014-03-14 18:52 ` David Grothe
2014-03-14 19:25 ` Kurt H Maier
2014-03-14 19:35 ` David Grothe
2014-03-14 21:04 ` David Grothe
2014-03-14 21:37 ` John Spencer
2014-03-15 0:09 ` Rich Felker
2014-03-15 0:22 ` Rich Felker
2014-03-14 16:47 ` Rich Felker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140314164720.GG184@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
--cc=support@Gcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).