[FFmpeg-devel] Hacks on FATE
Måns Rullgård
mans
Thu Jun 18 00:00:33 CEST 2009
Some of the FATE configurations are using decidedly non-standard
configure options. Some even apply PATCHES to the code. This is not
the way we want it to be.
Here's a summary of scary-looking things:
x86_32 MacOSX: --disable-decoder=cavs
Compiler bug?
x86_64 MacOSX: --extra-cflags="-m64" --extra-ldflags="-m64"
Does macos build 32-bit by default, or what?
x86_32 DOS: --extra-cflags='-U__STRICT_ANSI__ -fno-builtin' --disable-network
-U__STRICT_ANSI__ looks like a workaround for broken system headers.
What breaks without -fno-builtin? Can it be checked for in configure?
Why is --disable-network needed? Are more tests in configure needed?
x86_32 FreeBSD: --extra-cflags=-D__BSD_VISIBLE
x86_32 NetBSD: --extra-cflags=-D_NETBSD_SOURCE
These are presumably required to work around the broken system
headers (bktr.h) on these systems.
x86_32 OpenBSD: cavsdsp_mmx-fPIC-friendly.diff; CFLAGS='-fPIC -DPIC'
Does OpenBSD require PIC even for static builds? If so, this should
be handled in configure. And what's in the patch?
x86_32 OpenSolaris: sed -i -e 's/^\(SHFLAGS\)=\(.*\)/\1=-mimpure-text \2/' config.mak
The -mimpure-text option allows non-PIC in shared libs. This should
be set in configure.
Sparc Solaris 10 gcc 3.4.6: --disable-demuxer=mpc8
Compiler bug?
All Solaris: --extra-libs=/usr/lib/values-xpg6.o
We know what values-xpg6.o is about, but has this issue been
reported to the gcc bugtracker?
--
M?ns Rullg?rd
mans at mansr.com
More information about the ffmpeg-devel
mailing list