GNOME Bugzilla – Bug 706601
Windows compilation fails since libav v9.5
Last modified: 2013-08-28 10:24:19 UTC
gst-libav-git build fails because of following gcc error In file included from libavcodec/dxva2_internal.h:31:0, from libavcodec/dxva2.c:23: libavcodec/dxva2.h:34:18: fatal error: d3d9.h: No such file or directory compilation terminated. make[5]: *** [libavcodec/dxva2.o] Error 1 make[5]: Leaving directory `/c/Users/bmonkey/cerbero/sources/windows_x86/gst-libav-git-None/gst-libs/ext/libav' make[4]: *** [all-local] Error 2 make[4]: Leaving directory `/c/Users/bmonkey/cerbero/sources/windows_x86/gst-libav-git-None/gst-libs/ext' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/c/Users/bmonkey/cerbero/sources/windows_x86/gst-libav-git-None/gst-libs/ext' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/c/Users/bmonkey/cerbero/sources/windows_x86/gst-libav-git-None/gst-libs' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/c/Users/bmonkey/cerbero/sources/windows_x86/gst-libav-git-None' make: *** [all] Error 2 ***** Error running 'buildone' command: Recipe 'gst-libav-git' failed at the build step 'compile' After bisecting this is the failing commit 127202d6f65584891dabf92be031f0d170b0e7f1 is the first bad commit commit 127202d6f65584891dabf92be031f0d170b0e7f1 Author: Sebastian Dröge <sebastian.droege@collabora.co.uk> Date: Tue Apr 23 14:19:48 2013 +0200 libav: Update to v9.5 :040000 040000 bd801898525bd6f3d9f514bd2e4efe33bbc8477e 41a82dbb3be0f4137f78a1453f60224d0cc0033f M gst-libs Reverting 127202d6f65584891dabf92be031f0d170b0e7f1 helps, but libav has to be bisected between 9.4 and 9.5 for further investigation. Adding the headers manually via -I did not work, neither in cerbero, nor in autotools for ges-libav.
Created attachment 252813 [details] [review] 0001-configure-Disable-build-of-dxva2-and-vdpau-support-e.patch I assume it works if you pass --enable-dxva2 in configure.ac in the emblibav_configure_args? We can't make use of the dxva2 support in libav anyway so it could as well be disabled.