From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6137 Path: news.gmane.org!not-for-mail From: =?UTF-8?B?SsO2cmcgS3JhdXNl?= Newsgroups: gmane.linux.lib.musl.general Subject: why is there no __MUSL__ macro? Date: Thu, 11 Sep 2014 13:00:09 +0200 Message-ID: <541180B9.5070604@posteo.de> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------010402090502010405090901" X-Trace: ger.gmane.org 1410433217 7261 80.91.229.3 (11 Sep 2014 11:00:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 11 Sep 2014 11:00:17 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6150-gllmg-musl=m.gmane.org@lists.openwall.com Thu Sep 11 13:00:11 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 1XS26h-0001BE-7e for gllmg-musl@plane.gmane.org; Thu, 11 Sep 2014 13:00:07 +0200 Original-Received: (qmail 9876 invoked by uid 550); 11 Sep 2014 11:00:04 -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 9868 invoked from network); 11 Sep 2014 11:00:04 -0000 X-Virus-Scanned: amavisd-new at posteo.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 Xref: news.gmane.org gmane.linux.lib.musl.general:6137 Archived-At: This is a multi-part message in MIME format. --------------010402090502010405090901 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi, I am trying to add support for the musl toolchain to FFmpeg. FFmpeg needs support for library features defined in POSIX.1-2001 with XSI extension and the standards below. Currently configure probes the host and target libc by checking for defined macros like __GLIBC__ and __UCLIBC__. In case of glibc and uclibc it sets -D_XOPEN_SOURCE=600 properly. After this it checks for some combinations of hardware and the probed libc to set some more compile options, if necessary. I know that musl does not have a macro __MUSL__ and I have read the explanation. However, I don't understand what's meant by "[..] it's a bug to assume a certain implementation has particular properties rather than testing." and how does it affect the way FFmpeg probes for the libc. What could be a solution which supports musl? Many thanks! Jörg --------------010402090502010405090901 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hi,

I am trying to add support for the musl toolchain to FFmpeg.

FFmpeg needs support for library features defined in POSIX.1-2001 with XSI extension and the standards below. Currently configure probes the host and target libc by checking for defined macros like __GLIBC__ and __UCLIBC__. In case of glibc and uclibc it sets -D_XOPEN_SOURCE=600 properly.

After this it checks for some combinations of hardware and the probed libc to set some more compile options, if necessary.

I know that musl does not have a macro __MUSL__ and I have read the explanation. However, I don't understand what's meant by "[..] it's a bug to assume a certain implementation has particular properties rather than testing." and how does it affect the way FFmpeg probes for the libc.

What could be a solution which supports musl?

Many thanks!
Jörg
--------------010402090502010405090901--