[FFmpeg-devel] [PATCH 1/4] libavutil/error: fix build with musl toolchain

Reimar Döffinger Reimar.Doeffinger at gmx.de
Tue Sep 2 23:49:47 CEST 2014

On Tue, Sep 02, 2014 at 11:31:39PM +0200, Jörg Krause wrote:
> The maintainers of the musl C library states that looking for __GLIBC__ or
> __UCLIBC__ and making assumptions about the implemented feature set is not
> the best way. Instead <features.h> should be inspected for the specification
> of the feature test macros. Here are links to a discussion on the musl
> mailing list:

I don't know for sure, but I suspect features.h won't help you one bit
for the things that configure check was supposed to solve, like the
fact that some specific POSIX compliance flag on some platforms will
hide a specific feature with no way to get it back again, yet you
need the POSIX features enabled by that flag.
Unless you propose to test all 100s of combinations of flags until
we find one that looks like it works, which I'd object to on the
reason that configure is already too slow.

More information about the ffmpeg-devel mailing list