From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9736 Path: news.gmane.org!not-for-mail From: Kurt H Maier Newsgroups: gmane.linux.lib.musl.general Subject: Re: Why there's no __MUSL__ macro question Date: Wed, 23 Mar 2016 09:28:40 -0400 Message-ID: <20160323132840.GD69755@wopr.sciops.net> References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1458739737 19695 80.91.229.3 (23 Mar 2016 13:28:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 23 Mar 2016 13:28:57 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9749-gllmg-musl=m.gmane.org@lists.openwall.com Wed Mar 23 14:28:57 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1aiiqG-0004PH-8g for gllmg-musl@m.gmane.org; Wed, 23 Mar 2016 14:28:56 +0100 Original-Received: (qmail 17795 invoked by uid 550); 23 Mar 2016 13:28:54 -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 17771 invoked from network); 23 Mar 2016 13:28:53 -0000 Mail-Followup-To: musl@lists.openwall.com Content-Disposition: inline In-Reply-To: Xref: news.gmane.org gmane.linux.lib.musl.general:9736 Archived-At: On Wed, Mar 23, 2016 at 01:08:16PM +0000, Sérgio Marques wrote: > > How are we expected to solve this kind of problem if not by using the > __MUSL__ macro? The recommended solution is to fix the code to be portable, instead of installing yet another special-case workaround. In this case, wrapping the "#include " line in an #ifdef __GLIBC__ would be more appropriate than special-casing for musl, since musl is not the only environment that lacks execinfo.h. I suspect this code would also fail to build on cygwin, for instance. If there existed a __MUSL__ macro, the maintainers of software like this would just use it instead of writing portable code. By refusing to implement a __MUSL__ macro, musl is helping to urge projects in the right direction. khm