On Thu, May 12, 2011 at 05:30:04PM +0200, Diego Biurrun wrote: > > First off, it would be great to have a Cygwin FATE configuration again. > People do use Cygwin and we would profit from timely notification of > breakage.
Ronald would like to see FATE instances for - "THREAD_TYPE=2 THREADS=8 fate" - "THREAD_TYPE=1 THREADS=8 fate" I would like to have another one that enables all external libraries. Not all developers have all supported external libraries installed, so it's easy for breakage to slip through, as apparently just happened for libmp3lame. > Some FATE configurations enable postproc, others don't. I just > switched the defaults so that postproc gets enabled automatically > if --enable-gpl is passed to configure. So, FATE maintainers, please > drop --enable-postproc from your configure lines. This has happened for all but the ppc/darwin FATE instances, which are managed by varenet, who is varenet? > Now on to specific FATE configurations and their flags and hacks: > > * x86_32 + x86_64 / linux / suncc > > This configuration adds empty host CFLAGS with '--host-cflags=' and passes > '--disable-asm' to configure. Why? Is there something we should have > more or better tests for in configure? This is hopefully fixed now in configure, please drop '--host-cflags=' and holler if there still are problems. Diego _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
