From: "André Draszik" <git@andred.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libnl: musl fixes
Date: Mon, 22 Aug 2016 10:54:10 +0100 [thread overview]
Message-ID: <1471859650.3713.10.camel@andred.net> (raw)
In-Reply-To: <7A51C236-FD8D-424C-9468-5796F4E54E10@gmail.com>
On Sa, 2016-08-20 at 07:51 -0700, Khem Raj wrote:
> >
> >
> Thinking more on this, there is an alternative to use strerror_l() rather
> than strerror_r(), that will avoid the non-confirming versions issue,
> moreover
> strerror_() is now recommended by posix to replace strerror_r() usage.
>
> see
>
> http://austingroupbugs.net/view.php?id=655
>
> I think this is going to be a better solution since its portable.
Yeah, you're right. Let me cook up something...
Cheers,
Andre'
next prev parent reply other threads:[~2016-08-22 9:54 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
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 [this message]
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=1471859650.3713.10.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