[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMKF1soqNbYpoF83MmF1nfTer1=jb=rSugKekJHrfGTH75guaA@mail.gmail.com>
Date: Tue, 14 Jun 2016 07:43:34 -0700
From: Khem Raj <raj.khem@...il.com>
To: musl@...ts.openwall.com
Cc: Luca Barbato <lu_zero@...too.org>
Subject: Re: Dynamic linker name
On Jun 5, 2016 6:47 PM, "Lei Zhang" <zhanglei.april@...il.com> 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
There is a llvm clang patch for this already. Look at
https://github.com/kraj/meta-clang/tree/master/recipes-devtools/clang/clang
>
>
> Thanks,
> Lei
Content of type "text/html" skipped
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.
