* strerror_r and _GNU_SOURCE
@ 2018-08-05 0:54 W. Michael Petullo
2018-08-05 1:04 ` Rich Felker
0 siblings, 1 reply; 2+ messages in thread
From: W. Michael Petullo @ 2018-08-05 0:54 UTC (permalink / raw)
To: musl
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: strerror_r and _GNU_SOURCE
2018-08-05 0:54 strerror_r and _GNU_SOURCE W. Michael Petullo
@ 2018-08-05 1:04 ` Rich Felker
0 siblings, 0 replies; 2+ messages in thread
From: Rich Felker @ 2018-08-05 1:04 UTC (permalink / raw)
To: W. Michael Petullo; +Cc: musl
On Sat, Aug 04, 2018 at 08:54:08PM -0400, W. Michael Petullo wrote:
> 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?
No, musl explicitly does not suppore the GNU interfaces that conflict
with standard interfaces by the same name.
Rich
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-08-05 1:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-08-05 0:54 strerror_r and _GNU_SOURCE W. Michael Petullo
2018-08-05 1:04 ` Rich Felker
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).