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: Thu, 14 May 2020 08:40:47 +0000 [thread overview]
Message-ID: <embfd59b10-ed77-469d-8363-5c04fd07d9a9@elzian> (raw)
In-Reply-To: <20200513215115.GC21576@brightrain.aerifal.cx>
>> Relocatability and
>> self-containedness are where it's at.
>
>Would you be happy with TARGET=HOST=... giving this behavior while
>NATIVE=y additionally gives a real native compiler (that uses the
>existing library ecosystem)? Or should I make a new name for the
>latter?
I personally wouldn't mind, but I at least have used musl-cross-make
in tooling in places I don't work at anymore, and chances are the new
maintainers are not toolchain experts - so incompatible changes would
make upgrading more difficult for them.
It's a question of terminology, mostly. I always assumed "native" meant
"target=host"; you seem to be saying that it really means
"non-sysrooted",
which I would rather call "non-sysrooted" or "system compiler". And I
think most people understand "native" the same way as I do, as the
opposite of "cross". So, for maximum clarity, I think it would be wiser
to use another name when you mean "native and non-sysrooted compiler".
--
Laurent
next prev parent reply other threads:[~2020-05-14 8:41 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
2020-05-13 21:51 ` Rich Felker
2020-05-14 8:40 ` Laurent Bercot [this message]
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=embfd59b10-ed77-469d-8363-5c04fd07d9a9@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).