From: "Sidney Manning" <sidneym@codeaurora.org>
To: <musl@lists.openwall.com>
Subject: RE: relative link between libc.so and the dynamic linker
Date: Thu, 4 Aug 2016 13:09:54 -0500 [thread overview]
Message-ID: <04d401d1ee7b$67651180$362f3480$@codeaurora.org> (raw)
In-Reply-To: <20160804021919.GE15995@brightrain.aerifal.cx>
> -----Original Message-----
> From: Rich Felker [mailto:dalias@aerifal.cx] On Behalf Of Rich Felker
> Sent: Wednesday, August 03, 2016 9:19 PM
> To: musl@lists.openwall.com
> Subject: Re: [musl] relative link between libc.so and the dynamic linker
>
> On Wed, Aug 03, 2016 at 03:52:51PM -0500, Sidney Manning wrote:
> > I'd like to suggest making the symbolic link between libc.so and
> > ld-musl-<target>.so.1 relative rather than absolute. A relative path
> > makes movement between systems easier, in particular when one is
> > copying cross binaries to into a runtime environment.
>
> Are you sure this is actually the case if you use DESTDIR rather than
prefix for
> staging the cross toolchain libs in the sysroot? I think the current
behavior
> already works fine as long as you do it that way, but I may be mistaken.
>
Yes, DESTDIR will work for me. So for cross builds, setting
prefix/libdir/syslibdir to target relative locations and DESTDIR to the
location of the image root works in the way I wanted it to.
This might not be relevant for very many people but for those that nfs mount
their freshly built c-library for a runtime check would still see ld-musl
pointing the wrong libc.so until they chrooted.
Thanks,
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by
The Linux Foundation
next prev parent reply other threads:[~2016-08-04 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 20:52 Sidney Manning
2016-08-03 21:14 ` Kylie McClain
2016-08-04 2:19 ` Rich Felker
2016-08-04 18:09 ` Sidney Manning [this message]
2016-08-04 7:49 ` Khem Raj
2016-08-04 16:47 ` 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='04d401d1ee7b$67651180$362f3480$@codeaurora.org' \
--to=sidneym@codeaurora.org \
--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).