From: "W. Michael Petullo" <mike@flyn.org>
To: musl@lists.openwall.com
Subject: strerror_r and _GNU_SOURCE
Date: Sat, 4 Aug 2018 20:54:08 -0400 [thread overview]
Message-ID: <20180805005408.GA17226@imp.flyn.org> (raw)
When _GNU_SOURCE is defined, strerror_r should return a char *. Musl
1.1.19 declares strerror_r as:
int strerror_r (int, char *, size_t)
I have found that _GNU_SOURCE is defined when I build snort on OpenWrt
(OpenWrt uses musl). This causes the build to fail because snort expects
strerror_r to return a char * since _GNU_SOURCE is defined.
Is this a bug in musl?
--
Mike
:wq
next reply other threads:[~2018-08-05 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 0:54 W. Michael Petullo [this message]
2018-08-05 1:04 ` 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=20180805005408.GA17226@imp.flyn.org \
--to=mike@flyn.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).