Summary: | media-video/vlc-2.1.0: fail to build against libav. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexandre <alexandre.guimaraes> |
Component: | Current packages | Assignee: | Tom Wijsman (TomWij) (RETIRED) <tomwij> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alan.mckinnon, casta, derk.tebokkel, media-video |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alexandre
2013-10-27 03:02:56 UTC
Can you try again with =media-video/libav-9.10 and let me know if that works? Thank you very much in advance. This error IS with libav-9.10 if you turn off the vdpau flag it builds .. i.e. -vdpau .. seems current libav versions are less than what is required .. (other than the 9999's) If we look for the last commit in the 2.1.0 tag (shortlog, page 2) that changes the libav hash, we find this commit: http://git.videolan.org/?p=vlc/vlc-2.1.git;a=commit;h=c1844c967204754c6652d237ce8057abd668d055 If we look at the diff, we end up finding b1f9cdc37ff5d5b391d2cd9af737ab4e5a0fc1c0 which appears to be present in the 9.9 and the 9.10 tag: http://git.libav.org/?p=libav.git&a=search&h=refs%2Ftags%2Fv9.10&st=commit&s=b1f9cdc37ff5d5b391d2cd9af737ab4e5a0fc1c0 So, 9.10 should definitely be the right version as it should fit those requirements. However, somehow that still doesn't appear so; so, we need to dig down further on what the error is trying to exactly tell us. Since it now says that both versions need to be higher than a certain restriction; we don't yet know which one of both fails, so it would be nice to figure that out first. For libav-9.10, I have found the following: http://git.libav.org/?p=libav.git;a=blob;f=libavutil/version.h;h=1dbb11ca21e8e3484e7e1cdb2e1373fd0358bd90;hb=bb81b2b2e06abbf713094f8b77b4cbd550c02503 #define LIBAVUTIL_VERSION_MAJOR 52 #define LIBAVUTIL_VERSION_MINOR 3 #define LIBAVUTIL_VERSION_MICRO 0 http://git.libav.org/?p=libav.git;a=blob;f=libavcodec/version.h;h=348ce99f2ad1adfcc670b822e17b043d372c945d;hb=bb81b2b2e06abbf713094f8b77b4cbd550c02503 #define LIBAVCODEC_VERSION_MAJOR 54 #define LIBAVCODEC_VERSION_MINOR 35 #define LIBAVCODEC_VERSION_MICRO 0 As you can clearly see, 52.3.0 < 52.4.0 and 54.35.0 < 54.36.0 for libavcodec; so, indeed, 2.1.0 appears to need libav-9999. :S http://git.libav.org/?p=libav.git;a=blob;f=libavutil/version.h;hb=HEAD #define LIBAVUTIL_VERSION_MAJOR 52 #define LIBAVUTIL_VERSION_MINOR 16 #define LIBAVUTIL_VERSION_MICRO 0 http://git.libav.org/?p=libav.git;a=blob;f=libavcodec/version.h;hb=HEAD #define LIBAVCODEC_VERSION_MAJOR 55 #define LIBAVCODEC_VERSION_MINOR 22 #define LIBAVCODEC_VERSION_MICRO 0 Just as I thought, 52.16.0 > 52.4.0 and 55.22.0 > 54.36.0. Just to check the ffmpeg side; on ffmpeg-1.2.4 I get 52.18.100 and 54.92.100 respectively using pkgconfig; so, ffmpeg doesn't seem to have this problem. As a result of this, I am going to add a blocker: vdpau? ( !<media-libs/libav-9.11 ) I'm afraid you'll have to either use 9999 or await upstream to bring out a new version of libav, as I don't think anything can be done on the vlc side; an alternative could be to temporarily use ffmpeg. + 27 Oct 2013; Tom Wijsman <TomWij@gentoo.org> vlc-2.1.0.ebuild, + vlc-2.1.9999.ebuild, vlc-9999.ebuild: + Restrict libav to version >=9.11 when using vdpau USE flag, see bug #489534 + comment #4 for details; reported by Alexandre, Guillame Castagnino and Dark W + te Bokkel. Thank you for reporting this and helping to the new version's quality. Just a small update, I've mentioned media-libs/libav, but have corrected this to be media-video/libav before committing when checking for it to be a visible ATOM: - vdpau? ( >=x11-libs/libvdpau-0.6:0 ) + vdpau? ( >=x11-libs/libvdpau-0.6:0 !<media-video/libav-9.11 ) *** Bug 489622 has been marked as a duplicate of this bug. *** |