[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <020b01d1edc9$00bbc490$02334db0$@codeaurora.org>
Date: Wed, 3 Aug 2016 15:52:51 -0500
From: "Sidney Manning" <sidneym@...eaurora.org>
To: <musl@...ts.openwall.com>
Subject: relative link between libc.so and the dynamic linker
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
Thanks,
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by
The Linux Foundation
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.
