From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13106 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: strerror_r and _GNU_SOURCE Date: Sat, 4 Aug 2018 21:04:55 -0400 Message-ID: <20180805010455.GQ1392@brightrain.aerifal.cx> References: <20180805005408.GA17226@imp.flyn.org> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1533430987 16782 195.159.176.226 (5 Aug 2018 01:03:07 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 5 Aug 2018 01:03:07 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) Cc: musl@lists.openwall.com To: "W. Michael Petullo" Original-X-From: musl-return-13122-gllmg-musl=m.gmane.org@lists.openwall.com Sun Aug 05 03:03:03 2018 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1fm7Rn-0004Gs-86 for gllmg-musl@m.gmane.org; Sun, 05 Aug 2018 03:03:03 +0200 Original-Received: (qmail 20343 invoked by uid 550); 5 Aug 2018 01:05:11 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 20322 invoked from network); 5 Aug 2018 01:05:10 -0000 Content-Disposition: inline In-Reply-To: <20180805005408.GA17226@imp.flyn.org> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:13106 Archived-At: 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