From: Rich Felker <dalias@libc.org>
To: Philip Deegan <philip.deegan@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: make install permissions
Date: Mon, 6 Jun 2016 18:27:36 -0400 [thread overview]
Message-ID: <20160606222736.GT10893@brightrain.aerifal.cx> (raw)
In-Reply-To: <CALrcwjDvgmnegU1+mqZ+C-k6rkPNDxcH38ZSjTuaP8UQE5h8xw@mail.gmail.com>
On Mon, Jun 06, 2016 at 09:54:02PM +0100, Philip Deegan wrote:
> Hi,
>
> I'm trying out musl and I noticed that even when "--prefix" is used for
> "configure", "make install" still tries to put a symlink in "/lib".
>
> Is this intentional?
Yes. --syslibdir is not affected by --prefix because it's part of the
ABI. You can opt to override it at build time if you want to install
on the host as non-root, but as a result your binaries linked against
musl will contain a hard-coded path that's specific to your
installation and won't be easily usable on systems other than your
own.
If you just want to stage an installation for a chroot or cross root,
don't make the staging location part of the prefix but instead run
"make install DESTIR=...".
> I rather keep my system directories clean and isolate my dev stuff.
>
> Thanks
>
> PS. Is there a "musl-g++.specs" floating around anywhere?
In principle the same recipe as musl-gcc works for g++, just replacing
the name fo the command it invokes, but the c++ headers (or maybe the
precompiled versions thereof?) from a glibc-based host gcc encode lots
of glibc-specific assumptions, and badly break at compile time.
Linking to the libstdc++.a that was originally built against glibc
works okay though. If you can come up with a solution for the headers
problem, we can add a g++ wrapper, but I don't have the time or
interest to spend trying to figure that out myself.
Rich
next prev parent reply other threads:[~2016-06-06 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 20:54 Philip Deegan
2016-06-06 21:45 ` Szabolcs Nagy
2016-06-06 22:27 ` Rich Felker [this message]
2016-06-07 9:48 ` Philip Deegan
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=20160606222736.GT10893@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=philip.deegan@gmail.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).