From: Jeffrey Walton <noloader@gmail.com>
To: musl@lists.openwall.com
Cc: Bruno Haible <bruno@clisp.org>,
"Dmitry V. Levin" <ldv@altlinux.org>,
config-patches@gnu.org
Subject: Re: [musl] Re: OS detection wrong on Alpine Linux 3.10
Date: Tue, 22 Sep 2020 16:39:12 -0400 [thread overview]
Message-ID: <CAH8yC8mgZJf2zVj3irJ_itkbMk0rMbw2QXWWkAG8RxOdCSYQPA@mail.gmail.com> (raw)
In-Reply-To: <20200922184610.GI3265@brightrain.aerifal.cx>
On Tue, Sep 22, 2020 at 2:46 PM Rich Felker <dalias@libc.org> wrote:
> ...
> > > There is one kinda legitimate purpose for detecting specifically musl:
> >
> > It is not your role to tell us which code we write is "legitimate" and
> > which code is not. I am a grown-up programmer.
>
> I'm not trying to tell you you're not a grown-up programmer. I'm
> trying to tell you that the answer to the question you're asking ("is
> this musl?") is not meaningful for achieving what you presumably want
> to achieve -- assisting the program using autoconf tests in
> automatically producing a build that works on the intended host.
That assumes a project is Autotools based.
I know of at least four projects that don't use Autotools (or other
similar programs) because they don't want the dependency (and problems
that come with the dependency).
Speaking from experience, Autotools is a mess, especially for C++
projects. I would not wish it on an enemy.
Jeff
next prev parent reply other threads:[~2020-09-22 20:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4768019.hHWyC0TzgU@omega>
2020-09-20 10:12 ` Dmitry V. Levin
2020-09-20 11:19 ` Bruno Haible
2020-09-20 12:18 ` Ariadne Conill
2020-09-20 13:56 ` Szabolcs Nagy
2020-09-20 17:14 ` Rich Felker
2020-09-20 19:21 ` Bruno Haible
2020-09-20 20:58 ` Hadrien Lacour
2020-09-21 6:53 ` A. Wilcox
2020-09-21 11:46 ` Florian Weimer
2020-09-22 18:46 ` Rich Felker
2020-09-22 20:18 ` Bruno Haible
2020-09-22 20:33 ` Jeffrey Walton
2020-09-22 20:39 ` Jeffrey Walton [this message]
2020-09-22 21:04 ` Laurent Bercot
2020-09-22 21:17 ` Jeffrey Walton
2020-09-23 8:49 ` Laurent Bercot
2020-09-23 13:13 ` James Y Knight
2020-09-23 16:08 ` Rich Felker
2020-09-23 16:16 ` Jeffrey Walton
2020-09-23 16:26 ` Ariadne Conill
2020-09-23 16:57 ` Jeffrey Walton
2020-09-23 16:36 ` Rich Felker
2020-09-20 12:19 ` Ariadne Conill
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=CAH8yC8mgZJf2zVj3irJ_itkbMk0rMbw2QXWWkAG8RxOdCSYQPA@mail.gmail.com \
--to=noloader@gmail.com \
--cc=bruno@clisp.org \
--cc=config-patches@gnu.org \
--cc=ldv@altlinux.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).