mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Laurent Bercot" <ska-dietlibc@skarnet.org>
To: musl@lists.openwall.com
Subject: Re: [musl] Re: [musl-cross-make] [PATCH v2] litecross: Fix system header dir when building native toolchains
Date: Wed, 13 May 2020 20:04:10 +0000	[thread overview]
Message-ID: <em57f8394e-3ae9-4c36-9209-f1643c937abd@elzian> (raw)
In-Reply-To: <CAGw6cBuGHa3KUhHCnKx5U5Wqh1awPKFwDhRiM5W8e7rL+1Cqhw@mail.gmail.com>

>My patch is intended to just fix this incorrect path, not to change
>the meaning of NATIVE=y. Such a change should probably involve
>coordination of Zach van Rijn and Laurent Bercot, both of whom
>distribute pre-built native toolchains (currently containing a usr ->
>. symlink). Consumers of those toolchains probably expect a
>self-contained, relocatable toolchain, since that's what they are
>currently getting.

  Yes. I don't know about Zach, but what I want from the tool is indeed
for it to produce self-contained, relocatable toolchains, whether they
are cross- or native. Non-sysrooted toolchains are not very interesting
to me: they have value when you are building a distribution, but less
so when you are building entirely independently from the existing
distribution, which is often the case with musl on glibc-based distros.
Also, a sysrooted toolchain is perfectly usable as the system
toolchain - it just requires a couple symbolic links.

  I 100% support fixing mcm and avoiding the need to patch the produced
toolchains, but please don't change its semantics. Relocatability and
self-containedness are where it's at.

--
  Laurent


  reply	other threads:[~2020-05-13 20:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07  6:49 [musl-cross-make] [PATCH] " Michael Forney
2020-03-23  4:34 ` [musl] [musl-cross-make] [PATCH v2] " Michael Forney
2020-05-09  0:27   ` [musl] " Michael Forney
2020-05-10 16:35     ` Rich Felker
2020-05-10 20:35       ` Michael Forney
2020-05-10 21:52         ` Rich Felker
2020-05-13  8:18           ` Michael Forney
2020-05-13 14:37             ` Rich Felker
2020-05-13 18:48               ` Michael Forney
2020-05-13 18:55                 ` Rich Felker
2020-05-13 19:34                   ` Michael Forney
2020-05-13 20:04                     ` Laurent Bercot [this message]
2020-05-13 21:51                       ` Rich Felker
2020-05-14  8:40                         ` Laurent Bercot
2020-08-19 21:00       ` Michael Forney

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=em57f8394e-3ae9-4c36-9209-f1643c937abd@elzian \
    --to=ska-dietlibc@skarnet.org \
    --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).