From: Igmar Palsenberg <musl@palsenberg.com>
To: Musl list <musl@lists.openwall.com>
Subject: 'Proper' software writing
Date: Mon, 03 Sep 2012 15:55:47 +0200 [thread overview]
Message-ID: <5044B6E3.70203@palsenberg.com> (raw)
Hi,
When attempting to fix my own piece of software I've come to the
conclusing that writing somewhat portable software (glibc vs musl) is a
huge PITA.
I've ironed out most issues, but that left me with some questions :
- 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 ?
Regards,
Igmar
next reply other threads:[~2012-09-03 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 13:55 Igmar Palsenberg [this message]
2012-09-03 14:32 ` Szabolcs Nagy
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=5044B6E3.70203@palsenberg.com \
--to=musl@palsenberg.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).