From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: SUSv2 c89 compilation environment symbols missing
Date: Fri, 30 Dec 2016 17:54:04 -0500 [thread overview]
Message-ID: <20161230225404.GU1555@brightrain.aerifal.cx> (raw)
In-Reply-To: <97280ba1-9a3c-0f19-90db-5b313980621a@gmail.com>
On Fri, Dec 30, 2016 at 04:44:04PM -0600, Laine Gholson wrote:
> yes I know SUSv2 is obsolete, but then why does musl even bother to define _SC_XBS5_ILP32_OFF32 then?
I'm not sure; I suppose it could be removed. Since we match the
numeric values of the macros on glibc (for limited abi compat) I
probably just included all the ones glibc had.
Rich
> On 12/30/16 16:42, Rich Felker wrote:
> >On Fri, Dec 30, 2016 at 04:30:13PM -0600, Laine Gholson wrote:
> >>musl defines, e.g _SC_XBS5_ILP32_OFF32, but not _CS_XBS5_ILP32_OFF32_CFLAGS
> >>see http://pubs.opengroup.org/onlinepubs/7908799/xcu/getconf.html
> >
> >That's an ancient standard; the current one is here:
> >
> >http://pubs.opengroup.org/onlinepubs/9699919799/utilities/getconf.html
> >
> >It does not mention the macros you asked about. But it's also
> >describing the getconf utility, not the unistd.h header. The latter is
> >here:
> >
> >http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/unistd.h.html
> >
> >and I don't see anything about the above macros. For what it's worth,
> >even the old version corresponding to the page you linked doesn't seem
> >to specify them:
> >
> >http://pubs.opengroup.org/onlinepubs/7908799/xsh/unistd.h.html
> >
> >Rich
> >
next prev parent reply other threads:[~2016-12-30 22:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 22:30 Laine Gholson
2016-12-30 22:42 ` Rich Felker
2016-12-30 22:44 ` Laine Gholson
2016-12-30 22:54 ` Rich Felker [this message]
2017-01-17 23:36 ` Laine Gholson
2017-01-18 3:26 ` A. Wilcox
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=20161230225404.GU1555@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).