Summary: | x11-libs/libva-vdpau-driver-0.7.4-r5 fails: "error: conflicting types for ‘vdpau_CreateSurfaceFromV4L2Buf’" with x11-libs/libva-2.5.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paolo Pedroni <paolo.pedroni> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chicago, stoffepojken |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | libva-vdpau-driver-0.7.4-r5:20190709-074007.log.gz |
Description
Paolo Pedroni
2019-07-09 10:17:36 UTC
I also have this bug, it appeared in the last two days after upgrading to the 17.1 profile, though I don't think the two are related. This looks bogus. The definitions of vdpau_CreateSurfaceFromV4L2Buf are identical between src/vdpau_video.{c,h}.
The following line in the file says
> distcc[237] ERROR: compile /var/tmp/portage/x11-libs/libva-vdpau-driver-0.7.4-r5/work/libva-vdpau-driver-0.7.4/src/vdpau_video.c on localhost failed
Does it build with FEATURES=-distcc?
Also, for my own curiosity, why do you want to use VA-API if your video card's drivers natively support VDPAU? Just to add a little color -- here, there is no distcc employed and I can see: equery depends x11-libs/libva-vdpau-driver * These packages depend on x11-libs/libva-vdpau-driver: x11-libs/libva-2.5.0-r1 (video_cards_nvidia ? >=x11-libs/libva-vdpau-driver-0.7.4-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_riscv_lp64d(-)?,abi_riscv_lp64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) (video_cards_nouveau ? >=x11-libs/libva-vdpau-driver-0.7.4-r3[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_riscv_lp64d(-)?,abi_riscv_lp64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) (vdpau ? >=x11-libs/libva-vdpau-driver-0.7.4-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_riscv_lp64d(-)?,abi_riscv_lp64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) Which if I'm reading that right means x11-libs/libva-vdpau-driver gets pulled in simply by having a USE="vdpau" or a VIDEO_CARDS="nvidia" on x11-libs/libva. (In reply to Chicago from comment #1) > I also have this bug, it appeared in the last two days after upgrading to > the 17.1 profile, though I don't think the two are related. I also have this bug and I do have 17.1 profile since long (beta) It is since x11-libs/libva-2.5.0-rX with above version off: x11-libs/libva-vdpau-driver-0.7.4-r4 x11-libs/libva-vdpau-driver-0.7.4-r5 fail. First I change my USE vdpau in x11-libs/libva-2.5.0 to positive (it was disabled), since I saw that libva-vdpau-driver depends on libva. How does it make sense to disable it in libva? This should be a USE-depend in the libva-vdpau-driver ebuild !? But both of x11-libs/libva-vdpau-driver keep going to fail. But when downgrading to =x11-libs/libva-2.4.1-r1 then libva-vdpau-driver successfully builds again. same here, indeed, downgrading libva helps Wow, that was fun. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=34d5cc6fcf1d76c1c2833cb534717246c221214c commit 34d5cc6fcf1d76c1c2833cb534717246c221214c Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2019-07-15 23:35:46 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2019-07-15 23:42:46 +0000 x11-libs/libva-vdpau-driver: Fix build with >=x11-libs/libva-2.5.0 Closes: https://bugs.gentoo.org/689530 Signed-off-by: Matt Turner <mattst88@gentoo.org> ...au-driver-0.7.4-include-linux-videodev2.h.patch | 25 ++++++++++++++++++++++ .../libva-vdpau-driver-0.7.4-r5.ebuild | 1 + 2 files changed, 26 insertions(+) |