From: Jeffrey Walton <noloader@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [musl] Re: OS detection wrong on Alpine Linux 3.10
Date: Wed, 23 Sep 2020 12:57:18 -0400 [thread overview]
Message-ID: <CAH8yC8mOpSt1wW57m8DWs3UNwVYrGUGWMqobAOTnOJBJK699pA@mail.gmail.com> (raw)
In-Reply-To: <7bd0a1a7-ffad-fd02-21a1-e4c6f0400146@dereferenced.org>
On Wed, Sep 23, 2020 at 12:26 PM Ariadne Conill
<ariadne@dereferenced.org> wrote:
>
> Hello,
>
> On 2020-09-23 10:16, Jeffrey Walton wrote:
> > On Wed, Sep 23, 2020 at 12:08 PM Rich Felker <dalias@libc.org> wrote:
> >>
> >> On Wed, Sep 23, 2020 at 09:13:16AM -0400, James Y Knight wrote:
> >>>>
> >>>>> 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.
> >>
> >> I can't know whether you're "willing", but you're definitely not
> >> willing and able. "All the..." includes people's personal projects
> >> (from scratch or patches to existing ones) that you will never see,
> >> future systems that come into existence long past your involvement in
> >> the project or even your lifetime, etc.
> >
> > Unless something has changed recently, Botan, Crypto++ and OpenSSL are
> > still being carried by most Linux distributions. OpenSSL is also
> > regularly distributed as part of other OSes, like AIX, Android, BSDs,
> > iOS, OS X and Solaris.
>
> You are dead wrong on this topic. OpenSSL actually goes the other way
> and performs absolutely wacky tests like "are we running on big-endian
> amd64." Any cryptography library is going to have to perform feature
> tests (either at build time or run time) to determine whether features
> like hardware acceleration are possible.
Sorry, my bad for the confusion.
Botan, Crypto++ and OpenSSL do not perform Autoconf-like compile-time
feature tests.
Botan has a configure-like program, but it is used to select
components. Preprocessor macros are used instead of feature tests.
Crypto++ uses preprocessor macros. Preprocessor macros are used
instead of feature tests. (This is slowly changing in Crypto++).
OpenSSL uses a preconfigured profile. './Configure LIST' will list the
profiles. It uses info from the profile and preprocessor macros are
used instead of feature tests.
Jeff
next prev parent reply other threads:[~2020-09-23 16:57 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
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 [this message]
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=CAH8yC8mOpSt1wW57m8DWs3UNwVYrGUGWMqobAOTnOJBJK699pA@mail.gmail.com \
--to=noloader@gmail.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).