mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Jörg Krause" <jkrause@posteo.de>
To: musl@lists.openwall.com
Subject: Re: why is there no __MUSL__ macro?
Date: Thu, 11 Sep 2014 14:24:21 +0200	[thread overview]
Message-ID: <54119475.1090208@posteo.de> (raw)
In-Reply-To: <alpine.LNX.2.11.1409111306580.10045@jelaas.eu>


On 09/11/2014 01:17 PM, Jens wrote:
>
> On Thu, 11 Sep 2014, Jörg Krause wrote:
>> 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.
>
> Maybe the explanation in the FAQ could be a bit more verbose.

Maybe that would help :-)

> But if you stop and think for a bit you'll realize that __MUSL__ would 
> tell you next to nothing. musl and any other libc that is maintained 
> will change with time. You cannot assume a specific functionality by 
> checking for __MUSL__. Bugs will be fixed, functionality will be 
> implemented etc.

I see.

>
> Even if you could check for a specific version of musl you will do 
> most people a disservice since their libc/version wont be handled.
> If instead you check for a specific functionality, it will be 
> independent of libc and version of libc.

I am not sure what you mean with "check for a specific functionality"?

>
> A somewhat limited build of ffmpeg, atleast, works fine with musl:
> OPTPREFIX=opt/av
> configure --prefix=/$OPTPREFIX \
>  --enable-gpl\
>  --enable-small --disable-ffplay --disable-ffprobe --disable-ffserver\
>  --enable-libmp3lame\
>  --enable-libx264 \
>  --disable-network --cc=musl-gcc

I'm using a musl cross-compiling toolchain and the limited build even 
without mp3 and x264 fails for me:

./configure --enable-cross-compile\
  --cross-prefix=/home/joerg/x86_64-linux-musl/bin/x86_64-linux-musl-\
  --arch=x86_64 --target-os=linux\
  --prefix=/home/joerg/test/ffmpeg\
  --enable-gpl\
  --enable-small --disable-ffplay --disable-ffprobe --disable-ffserver\
  --disable-network
[...]
make: *** [libavformat/segment.o] Error 1



  reply	other threads:[~2014-09-11 12:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 11:00 Jörg Krause
2014-09-11 11:09 ` Laurent Bercot
2014-09-11 11:17   ` Szabolcs Nagy
2014-09-11 12:02     ` Jörg Krause
2014-09-11 12:38       ` Szabolcs Nagy
2014-09-11 13:33         ` Jörg Krause
2014-09-11 14:48           ` Szabolcs Nagy
2014-09-11 14:30   ` Christian Neukirchen
2014-09-11 11:17 ` Jens
2014-09-11 12:24   ` Jörg Krause [this message]
2014-09-11 14:53     ` Isaac Dunham
2014-09-12  7:39       ` Jörg Krause
2014-09-11 14:47 ` Natanael Copa
2014-09-12  7:35   ` Jörg Krause
2014-09-12 15:37     ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54119475.1090208@posteo.de \
    --to=jkrause@posteo.de \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).