Created attachment 399038 [details, diff] patch for libav-11.3.ebuild Possible regression was introduced in commit http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-video/libav/libav-9999.ebuild?r1=1.21&r2=1.22 Ebuild uses --extra-cflags="${CFLAGS}" to set CFLAGS, but --extra-cflags=-mfpu=neon seems to override it. I do not have arm device, so i can not test attached patch. Arm team, please help.
libav-11.3.ebuild,v 1.4 has the patch.
I am not sure if this bug should still be opened or, at least, keep blocking the stabilization one as the ebuild is fixed (but still waiting for arm testing... but, anyway, arm team will need to test it again for stabilization)
I suggest replacing --extra-cflags="${CFLAGS}" with --disable-optimizations and dropping "use neon && myconf+=( --extra-cflags=-mfpu=neon )" completely. This works perfectly with libvpx (see bug 547194).
--disable-optimizations will prevent build system from passing -O3 to compiler (I guess this was the reason for --extra-cflags="${CFLAGS}"). -mfpu=neon will be passed by the build system where needed. I'll test these changes when I have time and attach patch here.
Hmm. It seems libav is different. It's build system doesn't have a switch to enable neon (only to disable). Instead if -mfpu=neon is in CFLAGS then neon intrinsics are enabled automatically. So please ignore my previous comments. :) BTW the patch was already applied, so the bug can be closed. https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-video/libav/libav-11.3.ebuild?r1=1.3&r2=1.4
