From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] xterm: Fix latent issue found with musl
Date: Sat, 14 Dec 2019 00:58:15 +0200 [thread overview]
Message-ID: <20191213225815.GA8776@localhost> (raw)
In-Reply-To: <CAMKF1so-nxHanPu6Nv3arQmSNoMyHwVj43+Myd6ZNeY=qVHU6A@mail.gmail.com>
On Fri, Dec 13, 2019 at 01:55:33PM -0800, Khem Raj wrote:
> On Thu, Dec 12, 2019 at 8:37 PM Adrian Bunk <bunk@stusta.de> wrote:
> > On Thu, Dec 12, 2019 at 12:22:52PM -0800, Khem Raj wrote:
>...
> > > +_POSIX_SOURCE is app-defined not system
> >
> > This is true for musl, not for glibc.
> >
> > The handling of _POSIX_SOURCE and _POSIX_VERSION differs between musl
> > and glibc due to glibc supporting older POSIX versions, and glibc also
> > supporting developers of portable code to select some specific older
> > POSIX version.
> >
> No thats not right.
> _POSIX_SOURCE (like all FTMs) is
> defined by the application to request a feature/standards profile
> it's not libc telling you "this is posix" or anything like that.
It is also defined when _POSIX_C_SOURCE is defined, or _GNU_SOURCE,
or when the default non-strict gcc mode is used.
The latter means that it is in practice nearly always defined when the
libc supports applications written against older versions of POSIX.
> _POSIX_VERSION tells you that
>...
_POSIX_VERSION being defined tells you that you have unistd.h included.
With glibc the value of _POSIX_VERSION depends on what feature/standards
profile the application has requested.
cu
Adrian
next prev parent reply other threads:[~2019-12-13 22:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 20:22 [meta-oe][PATCH] hdf5: Upgrade to 1.8.21 Khem Raj
2019-12-12 20:22 ` [meta-networking][PATCH] libnftnl: upgrade 1.1.4 -> 1.1.5 Khem Raj
2019-12-12 20:22 ` [meta-oe][PATCH] xterm: Fix latent issue found with musl Khem Raj
2019-12-13 4:37 ` Adrian Bunk
2019-12-13 21:55 ` Khem Raj
2019-12-13 22:58 ` Adrian Bunk [this message]
2019-12-14 5:55 ` Khem Raj
2019-12-14 14:20 ` Adrian Bunk
2019-12-14 15:24 ` Khem Raj
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=20191213225815.GA8776@localhost \
--to=bunk@stusta.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.