https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: media-libs/libva-intel-media-driver-22.6.3 fails to compile. Discovered on: amd64 (internal ref: ci)
Created attachment 834239 [details] build.log.xz build log and emerge --info (compressed because it exceeds attachment limit, use 'xzless' to read it)
Error(s) that match a know pattern in addition to what has been reported in the summary: FAILED: media_driver/CMakeFiles/iHD_drv_video_COMMON.dir/__/media_softlet/linux/common/vp/ddi/ddi_vp_functions.cpp.o fatal: not a git repository (or any parent up to mount point /var/tmp) /var/tmp/portage/media-libs/libva-intel-media-driver-22.6.3/work/media-driver-intel-media-22.6.3/media_softlet/linux/common/vp/ddi/ddi_vp_functions.cpp:26:10: fatal error: va/va_dricommon.h: No such file or directory /var/tmp/portage/media-libs/libva-intel-media-driver-22.6.3/work/media-driver-intel-media-22.6.3/media_softlet/linux/common/vp/ddi/ddi_vp_functions.cpp:26:10: fatal error: va/va_dricommon.h: No such file or directory
Hm, thats strange. It can't reproduce that :/
Created attachment 835145 [details] Build log
I confirm that I hit this bug too.
I'm affected as well, but I think I found the reason for the error. The va/va_dricommon.h header is only present if media-libs/libva is installed with USE="X" enabled. After making this change, I'm now able to compile media-libs/libva-intel-media-driver again, regardless if USE="X" is enabled for the package itself or not.
(In reply to Johannes Penßel from comment #6) > I'm affected as well, but I think I found the reason for the error. The > va/va_dricommon.h header is only present if media-libs/libva is installed > with USE="X" enabled. After making this change, I'm now able to compile > media-libs/libva-intel-media-driver again, regardless if USE="X" is enabled > for the package itself or not. This worked for me too, emerging media-libs/libva with USE="X" enabled media-libs/libva-intel-media-driver to emerge normally with or without USE="X" for itself.
*** Bug 883557 has been marked as a duplicate of this bug. ***
ci has reproduced this issue with version 22.6.4 - Updating summary.