On Tue, Oct 17, 2017 at 09:10:43 +0200, ZikZak wrote: > Sorry for the top-post, default behaviour of GMAIL. > > Here is the latest config.log issued from configure after the latest pull: > http://gameclash.fr:11111/share/S97wTzASjYBBS6e5/config.log > BTW, now I have to add --enable-libvpx otherwise even VP8 is no longer > taken into account.
First, I have to ask: In your first mail, you indicated that despite your configure line, your compiled ffmpeg does not support libvpx_vp9. In a subsequent mail, you showed us a build failure. Those two don't match. What is the result from this config.log you gave us? Does it fail when linking, or does it successfully build an ffmpeg binary, but that binary does not have libvpx_vp9 support? That said: This config.log does its checks for libvpx_vp[89] support starting in line 11790, and it seems to succeed for both features. If you get no error while building, I don't see why the resulting ffmpeg shouldn't have libvpx_vp9 support. If you do get the mentioned error while linking, your libvpx seems to be missing some symbols. This can be either due to a miscompilation of said library, or due to some recent changes to its API/ABI which ffmpeg can't cope with. Moritz _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
