From: Khem Raj <raj.khem@gmail.com>
To: "Rafael Esp?ndola" <rafael.espindola@gmail.com>,
musl@lists.openwall.com, Luca Barbato <lu_zero@gentoo.org>
Subject: Re: Dynamic linker name
Date: Tue, 14 Jun 2016 08:09:50 -0700 [thread overview]
Message-ID: <CAMKF1spA_ndjjiPRS8_eQNdFsUXz66WEt=fWzDiznUcyHRch1A@mail.gmail.com> (raw)
In-Reply-To: <20160614150430.GP22574@port70.net>
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
On Jun 14, 2016 8:04 AM, "Szabolcs Nagy" <nsz@port70.net> wrote:
>
> * Khem Raj <raj.khem@gmail.com> [2016-06-14 07:43:34 -0700]:
> > On Jun 5, 2016 6:47 PM, "Lei Zhang" <zhanglei.april@gmail.com> wrote:
> > > 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?
> >
> > There is a llvm clang patch for this already. Look at
> >
> >
https://github.com/kraj/meta-clang/tree/master/recipes-devtools/clang/clang
>
> i think these should be upstreamed into clang and
> the recent r272662 clang commit should be reverted
> and the existing mips musl hacks should be fixed too.
I planned to do that but was off for few weeks
[-- Attachment #2: Type: text/html, Size: 1198 bytes --]
next prev parent reply other threads:[~2016-06-14 15:09 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
2016-06-14 14:43 ` Khem Raj
2016-06-14 15:04 ` Szabolcs Nagy
2016-06-14 15:09 ` Khem Raj [this message]
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='CAMKF1spA_ndjjiPRS8_eQNdFsUXz66WEt=fWzDiznUcyHRch1A@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=lu_zero@gentoo.org \
--cc=musl@lists.openwall.com \
--cc=rafael.espindola@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).