From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: dlopen'ing glibc linked libraries
Date: Tue, 21 Jan 2014 19:17:27 +0100 [thread overview]
Message-ID: <20140121181726.GL1685@port70.net> (raw)
In-Reply-To: <CAKDfeskchVQzrQF7HZKydJMT+yyaSmVGmRebpny-GnTebrRQ4g@mail.gmail.com>
* Gabriel Jacobo <gabomdq@gmail.com> [2014-01-21 12:44:14 -0200]:
> But my question was oriented towards what's the goal for providing "full"
> binary compatibility with glibc.
no, full bug compatibility is not a goal (that would defeat the
purpose of a new libc)
that said, most apis are binary compatible with glibc (even for c++)
if you see a missing symbol or other breakage then please report it
here is a list of known issues:
http://wiki.musl-libc.org/wiki/Functional_differences_from_glibc
it may be possible to solve a lot of compatibility issues with
preloading an extra lib next to musl, i experimented with running
applications with
export LD_LIBRARY_PATH=/usr/lib:/usr/lib/i386-linux-gnu:/lib/i386-linux-gnu
export LD_PRELOAD=./libcompat.so
/lib/ld-musl-i386.so /usr/bin/something
on a debian system and a lot of things work (except the loader
crashes occasionally due to a kernel bug..)
(for instance glibc linked libstdc++ works easily or i can compile
with a glibc linked gcc loaded by musl)
next prev parent reply other threads:[~2014-01-21 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 13:57 Gabriel Jacobo
2014-01-21 14:31 ` John Spencer
2014-01-21 14:44 ` Gabriel Jacobo
2014-01-21 16:28 ` John Spencer
2014-01-21 18:17 ` Szabolcs Nagy [this message]
2014-01-23 10:07 ` Szabolcs Nagy
2014-01-24 10:07 ` Justin Cormack
2014-01-24 13:41 ` Szabolcs Nagy
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=20140121181726.GL1685@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.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).