From: Bruno Haible <bruno@clisp.org>
To: Rich Felker <dalias@aerifal.cx>, musl@lists.openwall.com
Subject: installation without root privileges
Date: Sun, 17 Jun 2012 19:33:26 +0200 [thread overview]
Message-ID: <1369503.9MkYmHAvz4@linuix> (raw)
Hi,
When installing musl-0.9.1 according to the recipe of INSTALL, Option 1,
CC="gcc-32" \
./configure --prefix=/arch/x86-linux/inst-musl \
--exec-prefix=/arch/x86-linux/inst-musl \
--target=i686-unknown-linux-gnu \
CC="gcc-32"
the "make install" ends like this:
...
install -D -m 644 include/wctype.h /arch/x86-linux/inst-musl/include/wctype.h
install -D -m 644 include/wordexp.h /arch/x86-linux/inst-musl/include/wordexp.h
install -D tools/musl-gcc /arch/x86-linux/inst-musl/bin/musl-gcc
ln -sf /arch/x86-linux/inst-musl/lib/libc.so /lib/ld-musl-i386.so.1 || true
ln: could not create symbolic link „/lib/ld-musl-i386.so.1“: Permission denied
But the /arch/x86-linux/inst-musl/lib/musl-gcc.specs, section *link,
contains a reference to the file /lib/ld-musl-i386.so.1 that could not be
installed. My solution was to change this to read:
*link:
%(old_link) -dynamic-linker /arch/x86-linux/inst-musl/lib/libc.so -nostdlib
Suggestion: When --disable-gcc-wrapper is not passed to configure (this is
what distinguishes "Option 1" from "Option 2", right?), don't even attempt
to put a symlink into /lib. Simply always put the libc.so's real filename
into the *link section of musl-gcc.specs. The drawback is that executables
built with musl can typically not be transferred to a different machine
(because that machine will likely use a different installation directory
for musl).
Bruno
next reply other threads:[~2012-06-17 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 17:33 Bruno Haible [this message]
2012-06-17 20:52 ` Szabolcs Nagy
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=1369503.9MkYmHAvz4@linuix \
--to=bruno@clisp.org \
--cc=dalias@aerifal.cx \
--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).