From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libnl: musl fixes
Date: Fri, 12 Aug 2016 08:26:50 +0100 [thread overview]
Message-ID: <1470986810.4987.8.camel@andred.net> (raw)
In-Reply-To: <3A0FE7FC-807D-4CED-8673-DA28B5F36A88@gmail.com>
On Thu, 2016-08-11 at 22:45 -0700, Khem Raj wrote:
> >
> > On Aug 11, 2016, at 7:06 AM, André Draszik <git@andred.net> wrote:
> >
> > The libnl+musl combination has two issues at the moment:
> > a) a public header file #include's an incorrect file
> > (sys/poll.h instead of poll.h), which causes warnings and
> > potentially errors (-Werror) in a musl based system
> > b) musl only ever provides the XSI version of strerror_r()
> >
>
> yes so you can check for something like
> (_POSIX_C_SOURCE >= 200112L || _XOPEN_SOURCE >= 600) && ! _GNU_SOURCE
> use XSI version
> else use GNU version
Well, the feature test is supposed to be set by the user (libnl in this
case), and evaluated by the c library (musl). libnl explicitly sets
_GNU_SOURCE, i.e. it expects the glibc version.
Given musl doesn't provide the glibc version, and apart from implementing
the other version in musl, I don't see any viable alternative other than
what I posted.
One could #undefine _GNU_SOURCE and #define POSIX_C_SOURCE as appropriate
during compilation of the affected files, but that might have other side-
effects, and would be a major deviation from upstream...
Cheers,
Andre'
next prev parent reply other threads:[~2016-08-12 7:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 14:06 [PATCH] libnl: musl fixes André Draszik
2016-08-12 5:45 ` Khem Raj
2016-08-12 7:26 ` André Draszik [this message]
2016-08-12 7:28 ` Khem Raj
2016-08-12 7:42 ` André Draszik
2016-08-20 14:51 ` Khem Raj
2016-08-22 9:54 ` André Draszik
2016-08-26 10:42 ` André Draszik
2016-08-19 10:31 ` André Draszik
2016-08-19 16:50 ` 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=1470986810.4987.8.camel@andred.net \
--to=git@andred.net \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox