mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Lei Zhang <zhanglei.april@gmail.com>
Cc: musl@lists.openwall.com, Luca Barbato <lu_zero@gentoo.org>
Subject: Re: Dynamic linker name
Date: Sun, 5 Jun 2016 22:57:40 -0400	[thread overview]
Message-ID: <20160606025739.GR10893@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAOYuCc1yfzO4Rs9bP5XjaVp620P8xyq_FSnFJCfnWS5KejS3fg@mail.gmail.com>

On Mon, Jun 06, 2016 at 09:47:10AM +0800, Lei Zhang wrote:
> Hi,
> 
> I'm trying to make a few changes to clang/LLVM to make it work with
> musl, i.e. link executables against musl instead of glibc.
> 
> One of the changes involved is to tell clang where to find musl's
> dynamic linker. My question is: is musl's dynamic linker always named
> "ld-musl-$ARCH.so.1" and put under /lib?
> 
> More specifically, on a multilib system, which of the following is encouraged?
> 
> 1. /lib/ld-musl-{x86,x86_64}.so.1
> 2. /lib32/ld-musl-x86.so.1 and /lib64/ld-musl-x86_64.so.1

It's always /lib/, not /lib32/ or /lib64/.

Rich


  reply	other threads:[~2016-06-06  2:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06  1:47 Lei Zhang
2016-06-06  2:57 ` Rich Felker [this message]
2016-06-14 14:43 ` Khem Raj
2016-06-14 15:04   ` Szabolcs Nagy
2016-06-14 15:09     ` Khem Raj
2016-06-14 15:11     ` Rafael Espíndola
2016-06-14 15:56       ` Lei Zhang
2016-06-15  3:06         ` Lei Zhang
2016-06-15  7:10           ` Felix Janda
2016-06-15  8:16             ` Lei Zhang
2016-06-15  9:31               ` Luca Barbato
2016-06-15  9:39                 ` Lei Zhang
2016-06-15 13:00                   ` Bobby Bingham
2016-06-15 14:23                     ` Lei Zhang
2016-06-15 14:54                     ` Khem Raj

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=20160606025739.GR10893@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=lu_zero@gentoo.org \
    --cc=musl@lists.openwall.com \
    --cc=zhanglei.april@gmail.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).