Created attachment 897540 [details] libva-intel-media-driver-24.2.5 log file in xz format I'm on Gentoo stable branch via Calculate Linux but I've installed media-libs/libva-intel-media-driver from the testing branch. The update to media-libs/libva-intel-media-driver-24.2.5 fails during the compilation with the following error. I'm only pasting the relevant (hopefully) parts here, FAILED: media_driver/CMakeFiles/iHD_drv_video_SOFTLET_VP.dir/__/media_softlet/agnostic/common/vp/hal/packet/vp_vebox_cmd_packet.cpp.o ninja: build stopped: subcommand failed. ERROR: media-libs/libva-intel-media-driver-24.2.5::gentoo failed (compile phase): ninja -v -j3 -l0 failed Call stack: ebuild.sh, line 136: Called src_compile environment, line 2755: Called cmake-multilib_src_compile environment, line 829: Called multilib-minimal_src_compile environment, line 1981: Called multilib_foreach_abi 'multilib-minimal_abi_src_compile' environment, line 2248: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' environment, line 1941: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' environment, line 1939: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_compile' environment, line 543: Called multilib-minimal_abi_src_compile environment, line 1975: Called multilib_src_compile environment, line 2468: Called cmake_src_compile environment, line 947: Called cmake_build environment, line 914: Called eninja environment, line 1389: Called die The specific snippet of code: "$@" || die -n "${*} failed" The above behavior has been observed multiple times. It is always reproducible on my system.
Notes on the build.log: 1. The filename is .xz but it's bzip2? 2. It's a tarball so it should be foo.tar.bz2 Anyway, Calculate Linux is not Gentoo. Please rpeort it to them.
It was a mistake on my part to name a bzip2 file as an xz file. I can re-upload it with the correct name if you wish. Calculate Linux is based on Gentoo and is 100% backward compatible with it so I don't see any point in this as the reason for marking this bug invalid. BTW Calculate is listed on the Gentoo wiki page 'Distributions based on Gentoo'. I'm still not allowed to post links here but if you search the GitHub repository of intel/media-driver for the issue number 1827, you'll find that the bug reported here is remarkably similar to that one. I'll request you to consider the above points and re-open this bug for further inspection.
By default, bug reports for derivatives should go there first, given we have no idea what they changed. If they changed nothing, they wouldn't exist at all.
Will it help you in reconsidering if I post the output of `emerge --info` or any other data you might need?
I think someone gave some analysis on IRC I'll take a look at when I'm home.
(In reply to Sam James from comment #5) > I think someone gave some analysis on IRC I'll take a look at when I'm home. That'll be great! Wishing you a happy Sunday ahead!
Created attachment 897616 [details] Output of emerge --info command Adding a file containing the output of emerge --info '=media-libs/libva-intel-media-driver-24.2.5::gentoo' command with the expectation that this will provide additional required information.
Seeing the same thing; this hopefully illuminates things (not for me unfortunately): $ grep -ai ' error' build.log /var/calculate/tmp/portage/media-libs/libva-intel-media-driver-24.2.5/work/media-driver-intel-media-24.2.5/media_softlet/agnostic/common/vp/hal/packet/vp_vebox_cmd_packet.cpp:3066:25: error: ‘VPHAL_VEBOX_RGB32’ was not declared in this scope; did you mean ‘VPHAL_VEBOX_Y416’? /var/calculate/tmp/portage/media-libs/libva-intel-media-driver-24.2.5/work/media-driver-intel-media-24.2.5/media_softlet/agnostic/common/vp/hal/packet/vp_vebox_cmd_packet.cpp:3070:25: error: ‘VPHAL_VEBOX_AYUV’ was not declared in this scope; did you mean ‘VPHAL_VEBOX_ACE’? /var/calculate/tmp/portage/media-libs/libva-intel-media-driver-24.2.5/work/media-driver-intel-media-24.2.5/media_softlet/agnostic/common/vp/hal/packet/vp_vebox_cmd_packet.cpp:3077:25: error: ‘VPHAL_VEBOX_RGB64’ was not declared in this scope; did you mean ‘VPHAL_VEBOX_Y416’? * ERROR: media-libs/libva-intel-media-driver-24.2.5::gentoo failed (compile phase):
Thanks! And I'm sorry for being grumpy.
negril/parona pointed out that we need https://github.com/intel/gmmlib/commit/40348e9a75ecc280cf156d4ef7fd48dc4acbf84e in media-libs/gmmlib, i.e. >=22.3.20.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7650157a7286906c865f2144395ff4fcabc2151c commit 7650157a7286906c865f2144395ff4fcabc2151c Author: Sam James <sam@gentoo.org> AuthorDate: 2024-07-15 02:49:08 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-07-15 02:49:49 +0000 media-libs/libva-intel-media-driver: fix minimum gmmlib version, sync live We need >=22.3.20 for upstream commit 40348e9a75ecc280cf156d4ef7fd48dc4acbf84e which defines VPHAL_VEBOX_AYUV and friends. Sync live while we're here. Closes: https://bugs.gentoo.org/936010 Signed-off-by: Sam James <sam@gentoo.org> .../libva-intel-media-driver/libva-intel-media-driver-24.2.5.ebuild | 2 +- .../libva-intel-media-driver/libva-intel-media-driver-9999.ebuild | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
Thank you very much Sam James for fixing this bug!
