From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Cc: CLFS development discussion <clfs-dev@lists.cross-lfs.org>,
CLFS Support <clfs-support@lists.cross-lfs.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregor Richards <gr@purdue.edu>
Subject: Re: Re: [Clfs-dev] CLFS embedded book switches to musl-libc
Date: Tue, 22 Oct 2013 17:08:46 -0400 [thread overview]
Message-ID: <20131022210846.GZ20515@brightrain.aerifal.cx> (raw)
In-Reply-To: <CACgAsMdTDBH2cejyPG7p2PL7bqtf7rSCfzskJjcCKG72L8rO8A@mail.gmail.com>
On Tue, Oct 22, 2013 at 02:58:24PM -0400, Kevyn-Alexandre Paré wrote:
> Hi Andrew,
>
> So far so good! Very interesting that you passed to musl and I'm happy
> to start playing with it!
>
> Couple of question about Manual:
> You refer to glibc [1] should you replace that glibc with musl libc or
> glibc(musl) our simply libc?
>
> For the musl installation [2], the make install have an error that
> seem to be fix with the next command you propose:
>
> ../tools/install.sh -D -m 644 lib/crt1.o
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/crt1.o
> ../tools/install.sh -D -m 644 lib/Scrt1.o
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/Scrt1.o
> ../tools/install.sh -D -m 644 lib/crti.o
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/crti.o
> ../tools/install.sh -D -m 644 lib/crtn.o
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/crtn.o
> ../tools/install.sh -D -m 644 lib/libc.a
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/libc.a
> ../tools/install.sh -D -m 755 lib/libc.so
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/libc.so
> ../tools/install.sh -D -m 644 lib/libm.a
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/libm.a
> ../tools/install.sh -D -m 644 lib/librt.a
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/librt.a
> ../tools/install.sh -D -m 644 lib/libpthread.a
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/libpthread.a
> ../tools/install.sh -D -m 644 lib/libcrypt.a
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/libcrypt.a
> ../tools/install.sh -D -m 644 lib/libutil.a
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/libutil.a
> ../tools/install.sh -D -m 644 lib/libxnet.a
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/libxnet.a
> ../tools/install.sh -D -m 644 lib/libresolv.a
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/libresolv.a
> ../tools/install.sh -D -m 644 lib/libdl.a
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/libdl.a
> ../tools/install.sh -D -l
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/lib/libc.so
> /lib/ld-musl-arm.so.1 || true
> ln: failed to create symbolic link `/lib/ld-musl-arm.so.1.tmp.47054':
> Permission denied
> ../tools/install.sh -D -m 644 arch/arm/bits/alltypes.h
> /mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/include/bits/alltypes.h
This (attempting to install the dynamic linker symlink in /lib) is
caused by specifying the installation location
/mnt/clfs/cross-tools/armv7a-unknown-linux-musleabi/ as part of the
prefix rather than as the DESTDIR at "make install" time. If this is
part of the installation into the new filesystem root that will be
later used as chroot or the root for booting, DESTDIR is the proper
approach. If this is just a temporary musl build for use in
bootstrapping, the current --prefix is fine, but you also need either
--syslibdir or --disable-shared.
Rich
next prev parent reply other threads:[~2013-10-22 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 19:59 Andrew Bradford
2013-10-16 20:38 ` John Spencer
2013-10-16 20:46 ` Andrew Bradford
2013-10-16 21:22 ` John Spencer
2013-10-17 12:50 ` Andrew Bradford
2013-10-22 18:58 ` [Clfs-dev] " Kevyn-Alexandre Paré
2013-10-22 21:08 ` Rich Felker [this message]
2013-10-23 11:07 ` [musl] " Andrew Bradford
2013-10-23 14:13 ` 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=20131022210846.GZ20515@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=clfs-dev@lists.cross-lfs.org \
--cc=clfs-support@lists.cross-lfs.org \
--cc=gr@purdue.edu \
--cc=musl@lists.openwall.com \
--cc=thomas.petazzoni@free-electrons.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).