From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: 'Proper' software writing
Date: Mon, 3 Sep 2012 16:32:42 +0200 [thread overview]
Message-ID: <20120903143242.GT1104@port70.net> (raw)
In-Reply-To: <5044B6E3.70203@palsenberg.com>
* Igmar Palsenberg <musl@palsenberg.com> [2012-09-03 15:55:47 +0200]:
> - Why use _BSD_SOURCE and _GNU_SOURCE at all ? What is the argument of
> not exposing *ALL* stuff that is in musl ?
> - Is there a way to do proper feature detection ? I tried autoscan from
> autotools, but the outcome wanted to make me cry. It missed about all
> that is important.
>
> Any comments / suggestions ?
>
see the archive, we just had a discussion about this
here is the summary:
http://www.openwall.com/lists/musl/2012/09/03/1
currently the easy way to work around broken code is
to add -D_GNU_SOURCE to the CFLAGS
exposing all stuff by default is not what you want:
many of the symbols are obsolete/broken, there are bsd
symbols not present in glibc and simple symbols that
violate the standard namespace (so they can easily cause
problems if made visible by default)
next prev parent reply other threads:[~2012-09-03 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 13:55 Igmar Palsenberg
2012-09-03 14:32 ` Szabolcs Nagy [this message]
2012-09-04 1:50 ` Rich Felker
2012-09-04 9:41 ` Igmar Palsenberg
2012-09-04 11:18 ` Igmar Palsenberg
2012-09-04 13:32 ` 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=20120903143242.GT1104@port70.net \
--to=nsz@port70.net \
--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).