From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: future of compiler wrappers
Date: Tue, 3 Jul 2018 09:25:55 +0200 [thread overview]
Message-ID: <20180703092555.2c29f15c@inria.fr> (raw)
In-Reply-To: <20180702165043.GK1392@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
Hello Rich,
On Mon, 2 Jul 2018 12:50:43 -0400 Rich Felker <dalias@libc.org> wrote:
> I don't want it abandoned. That's why I'm asking and trying to gauge
> if there's interest in maintaining it separately. I agree that it
> meets some people's needs well enough and it's convenient, but I feel
> like having it as something you fetch/install separately would be
> better ux/presentation in many ways, in that it wouldn't suggest it's
> the "right" way to use musl and would ensure that users are aware
> they're using something that has limited functionality, rather than
> thinking they're hitting problems with musl.
I use musl in teaching, because it is the only variant of the C
library where I can have full standard conformance for atomics and
threads. The university system on which the students are working is
something that I have not much control of, and forcing it to allways
have the latest .dep package of musl installed was quite a challenge.
So anything that changed that situation, would make this even more
fragile. Generally, I think that are a lot of people out there that
don't completely control their developement environment. I would be
nice if withdrawing musl-gcc from musl could wait until the
replacement is a well-established package in the major distributions.
On the other hand I agree that it would probably be a good idea to
have a compiler wrapper package that is independent of musl and that
allows to combine more or less any compiler with any of the C
libraries. It is just annoying that the compiler frontends don't have
easy to use options for this in the first place.
Thanks
Jens
--
:: INRIA Nancy Grand Est ::: Camus ::::::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536 ::
:: :::::::::::::::::::::: gsm France : +33 651400183 ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2018-07-03 7:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 0:11 Rich Felker
2018-07-02 15:28 ` Markus Wichmann
2018-07-02 16:00 ` Assaf Gordon
2018-07-02 16:50 ` Rich Felker
2018-07-03 7:25 ` Jens Gustedt [this message]
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=20180703092555.2c29f15c@inria.fr \
--to=jens.gustedt@inria.fr \
--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).