From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6151 Path: news.gmane.org!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: why is there no __MUSL__ macro? Date: Thu, 11 Sep 2014 16:48:55 +0200 Message-ID: <20140911144855.GM21835@port70.net> References: <541180B9.5070604@posteo.de> <541182D3.5010104@skarnet.org> <20140911111721.GG21835@port70.net> <54118F73.2020807@posteo.de> <20140911123800.GI21835@port70.net> <5411A49C.20808@posteo.de> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1410446955 28352 80.91.229.3 (11 Sep 2014 14:49:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 11 Sep 2014 14:49:15 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6164-gllmg-musl=m.gmane.org@lists.openwall.com Thu Sep 11 16:49:08 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1XS5gK-0002a6-5c for gllmg-musl@plane.gmane.org; Thu, 11 Sep 2014 16:49:08 +0200 Original-Received: (qmail 18066 invoked by uid 550); 11 Sep 2014 14:49:07 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 18058 invoked from network); 11 Sep 2014 14:49:07 -0000 Mail-Followup-To: musl@lists.openwall.com Content-Disposition: inline In-Reply-To: <5411A49C.20808@posteo.de> User-Agent: Mutt/1.5.23 (2014-03-12) Xref: news.gmane.org gmane.linux.lib.musl.general:6151 Archived-At: * J?rg Krause [2014-09-11 15:33:16 +0200]: > eg, in FFmpeg/libavutils uses strerror_r which is implemented as a > XSI-compliant and a GNU-specific version. If I want to be sure to get the > XSI-compliant version, I unset _GNU_SOURCE and set _XOPEN_SOURCE=600. So I > do not need any further testing here, right? yes, using feature test macros should work (unless you want to support some very old version of the libc)