mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: musl@lists.openwall.com
Subject: Re: relative link between libc.so and the dynamic linker
Date: Thu, 4 Aug 2016 00:49:57 -0700	[thread overview]
Message-ID: <7193C5A6-EAE6-4EBE-958D-58D90D4409A0@gmail.com> (raw)
In-Reply-To: <020b01d1edc9$00bbc490$02334db0$@codeaurora.org>

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]


> On Aug 3, 2016, at 1:52 PM, Sidney Manning <sidneym@codeaurora.org> 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.
> 
> diff --git a/tools/install.sh b/tools/install.sh
> index d913b60..1c102f5 100755
> --- a/tools/install.sh
> +++ b/tools/install.sh
> @@ -48,7 +48,7 @@ trap 'rm -f "$tmp"' EXIT INT QUIT TERM HUP
> umask 077
> 
> if test "$symlink" ; then
> -ln -s "$1" "$tmp"
> +ln -s -r "$1" "$tmp"
> else
> cat < "$1" > "$tmp"
> chmod "$mode" "$tmp"
> 
> 
> 
> The final result would look something like this:
> ld-musl-x86_64.so.1 -> ../usr/lib/libc.so
> 
> Rather than:
> ld-musl-x86_64.so.1 -> /tmp/musl/install/usr/lib/libc.so

Does something like this help you

https://github.com/kraj/musl/commit/c0b1bd4e6bb60b8167e1f4a40beccff7f8871691



[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 204 bytes --]

  parent reply	other threads:[~2016-08-04  7:49 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
2016-08-04  7:49 ` Khem Raj [this message]
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=7193C5A6-EAE6-4EBE-958D-58D90D4409A0@gmail.com \
    --to=raj.khem@gmail.com \
    --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).