mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: Best bikeshed ever (feature test macros)
Date: Mon, 27 Aug 2012 11:08:30 -0700	[thread overview]
Message-ID: <20120827110830.43d1a74a@newbook> (raw)
In-Reply-To: <20120824214138.GA17792@brightrain.aerifal.cx>

On Fri, 24 Aug 2012 17:41:38 -0400
Rich Felker <dalias@aerifal.cx> wrote:

> Hi all,
> 
> Feature test macros (the fun -D_POSIX_C_SOURCE=200809L, -D_GNU_SOURCE,
> etc. things everybody gets wrong) have been one of the more
> controversial aspects of musl, particularly the fact that musl
> presents by default a straight ISO C conforming environment with no
> POSIX, traditional Unix, etc. stuff offending the pristine C
> namespace, and requires the use of one or more feature test macros to
> get basically _ANY_ typical unixy software to build.

I have built a few programs without extra CFLAGS.
(two of them being nebula & cmix)
> 
> 1. Leaving everything as it is.
> 

> 
> 2. Making the kitchen sink (_GNU_SOURCE) available by default.

This can be done the same way as 3, but it does mean a lot of extra
verbiage in the headers. 
Name collisions are something I've run into, though they're fairly
trivial to fix in my experience.
All told, I'd say it's practical but maybe not desirable.
And if you *are* going to make everything available, also make the
strl* functions and fgetln available, so software doesn't pull in its
own version due to broken tests (haven't noticed this happening,
but...).

> 3. Making only some limited subset (e.g. POSIX base) available by
> default.

I'd prefer some variant of 3. And the _XOPEN_SOURCE=600 || _BSD_SOURCE
suggestion does sound fairly reasonable except for some headers, like
<math.h>

Isaac Dunham



  parent reply	other threads:[~2012-08-27 18:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 21:41 Rich Felker
2012-08-24 22:24 ` Gregor Richards
2012-08-24 23:59 ` Szabolcs Nagy
2012-08-25  7:35 ` orc
2012-08-25 12:32   ` Rich Felker
2012-08-25 15:29     ` orc
2012-08-25  9:11 ` Luca Barbato
2012-08-27 18:08 ` Isaac Dunham [this message]
2012-08-29  5:34 ` philomath
2012-08-29 13:49   ` Rich Felker
2012-08-29 14:01     ` Gregor Richards
2012-08-29 14:43       ` Rich Felker
2012-08-29 15:08         ` Bobby Bingham
2012-08-29 15:23           ` Rich Felker
2012-08-29 17:17             ` Gregor Richards
2012-08-29 17:59       ` Isaac Dunham
2012-08-29 18:08         ` Rich Felker
2012-09-02  8:48 ` Arvid E. Picciani
2012-09-02 15:19   ` Rich Felker
2012-09-02 15:27     ` Arvid E. Picciani
2012-09-02 15:44       ` Rich Felker
2012-09-02 17:00 ` nwmcsween
2012-09-02 17:06   ` Gregor Richards
2012-09-02 17:13     ` Rich Felker
2012-09-02 17:18       ` Gregor Richards
2012-09-02 17:10   ` Rich Felker

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=20120827110830.43d1a74a@newbook \
    --to=idunham@lavabit.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).