From: James Y Knight <jyknight@google.com>
To: musl@lists.openwall.com
Subject: Re: [musl] Re: OS detection wrong on Alpine Linux 3.10
Date: Wed, 23 Sep 2020 09:13:16 -0400 [thread overview]
Message-ID: <CAA2zVHrV08zfWuqnsMkbeYUiLh+bA3vzNw2QDgybh6qwGQBHGw@mail.gmail.com> (raw)
In-Reply-To: <emd066d42c-4dbc-468a-b93a-2aebbdaa72e1@elzian>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
>
> >All I need to know is what version of Musl I am dealing with and I can
> >configure myself.
>
> Are you willing to maintain an #ifdef forest for all the versions of
> all the libcs and all the kernels your programs may be used with, so
> you can list exhaustively the available features in every configuration?
>
At the risk of jumping in on a question asked of someone else: yes,
absolutely! (Not _all_ available features of course, just the ones
required.)
There are generally not that many nonstandard features you'd want to use in
a typical program, and using an ifdef forest to implement an abstraction
layer around those couple items is just fine.
[-- Attachment #2: Type: text/html, Size: 960 bytes --]
next prev parent reply other threads:[~2020-09-23 13:13 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
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 [this message]
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=CAA2zVHrV08zfWuqnsMkbeYUiLh+bA3vzNw2QDgybh6qwGQBHGw@mail.gmail.com \
--to=jyknight@google.com \
--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).