mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Dynamic linker committed!
Date: Sun, 19 Jun 2011 08:49:59 -0400	[thread overview]
Message-ID: <20110619124959.GR12592@brightrain.aerifal.cx> (raw)

Greetings,

The dynamic linker has been committed and is ready for testing. To use
it, libc.so needs to be installed somewhere convenient and the
-Wl,-dynamic-linker option needs to be passed to glibc to tell it
which dynamic linker to use. The eventual name I intend to use (short
of better suggestions) is /lib/ld-musl-$ARCH.so.1 where $ARCH is i386,
x86_64, etc. The idea of including $ARCH is that if a system can
support multiple archs' binaries (e.g. i386 and x86_64) no additional
special-casing of the dynamic linker name is required.

At present, the library search path is hard coded as
/lib:/usr/local/lib:/usr/lib. Obviously this only works if you have a
musl-based system rather than having glibc stuff in those paths, so
until I add configurability, you might want to edit the path in
src/ldso/dynamic.c manually when building.

Also note that there is no support for LD_* env vars, which in turn
means no support for the "ldd" program. Some support may be added
later.

My plan is to fix up some of these issues over the next week and make
an experimental release for more widespread testing, then move on to
the 0.8.x series with official dynamic linking support including the
addition of dlopen/dlsym functionality. This should in turn make it
possible to use much of the important previously-unusable software
like python, X.org, etc. with musl.

Rich


             reply	other threads:[~2011-06-19 12:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-19 12:49 Rich Felker [this message]
2011-06-25  6:02 ` Rich Felker

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=20110619124959.GR12592@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).