From: Chris Hall <musl@gmch.uk>
To: musl@lists.openwall.com
Subject: Re: Detecting musl at compile and/or configure time
Date: Sun, 30 Jun 2019 12:48:55 +0100 [thread overview]
Message-ID: <7dfceb33-b903-de2a-7abe-825f44512f0c@gmch.uk> (raw)
In-Reply-To: <20190629135859.GA21055@port70.net>
On 29/06/2019 14:58, Szabolcs Nagy wrote:
>> On 06/29/19 06:48, Chris Hall wrote:
>>>
>>> Is there a supported way of detecting that one is building against the
>>> musl libc ?
>>>
>>> At compile time I can, of course, detect glibc because it sets __GLIBC__
>>> etc. For macOS I can see _DARWIN_FEATURE_xxx macros. The BSDs mostly
>>> give themselves away. But for musl I have not found anything :-(
...
> note that __GLIBC__ does not detect glibc: uclibc defines it too.
Happily it has the courtesy to also:
#define __UCLIBC__ 1
> you really want to configure check for particular features
> instead of detecting the libc (which is a moving target,
> ppl can patch it or change it over time)
In the limit, yes. I'm interested in how far one can get without the
need for configure/cmake/etc. -- accepting that means being quite
conservative in the choice of features to use (and assuming that the
target system is reasonably up to date).
Of course, for major issues -- eg epoll vs kqueue or netlink vs routeing
sockets -- it's the underlying OS that really matters. Detecting the OS
at compile time seems reasonably effective (also the compiler and the
processor). Detecting the libc feels like it should be a small step to
complete the picture.
Chris
next prev parent reply other threads:[~2019-06-30 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1561802993.8028.ezmlm@lists.openwall.com>
2019-06-29 11:48 ` Chris Hall
2019-06-29 13:27 ` A. Wilcox
2019-06-29 13:58 ` Szabolcs Nagy
2019-06-30 11:48 ` Chris Hall [this message]
2019-07-07 18:17 ` malloc() alignment and max_align_t Chris Hall
2019-07-07 19:22 ` Markus Wichmann
2019-07-08 0:16 ` Rich Felker
[not found] <26f5537f-a876-209c-a27c-cd2619f5c834@gmch.uk>
2019-06-30 12:03 ` Fwd: Re: Detecting musl at compile and/or configure time Chris Hall
2019-06-30 12:28 ` Samuel Holland
2019-06-30 14:30 ` Chris Hall
2019-06-30 14:54 ` Jeffrey Walton
2019-07-02 12:19 ` Florian Weimer
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=7dfceb33-b903-de2a-7abe-825f44512f0c@gmch.uk \
--to=musl@gmch.uk \
--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).