Summary: | media-libs/mesa[opencl] blocks intel users | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | axiator, luke, paolo.pedroni, skruppy+gentoo, soprwa, t-mo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pacho Ramos
2019-11-06 10:17:14 UTC
I've erred on the side of "make the user understand what they're enabling" because I grew tired of users filing bugs about not getting what they expect when they enable gallium-only USE flags for VIDEO_CARDS=i965. We could replace libclc's REQUIRED_USE with some warnings or something. Please make a suggestion. I don't understand the issue with that gallium-only USEs and i965 in VIDEO_CARDS :/ Mesa ebuild is already forcing "classic" for VIDEO_CARDS=i965 Thanks for the explanation (In reply to Pacho Ramos from comment #2) > I don't understand the issue with that gallium-only USEs and i965 in > VIDEO_CARDS :/ > > Mesa ebuild is already forcing "classic" for VIDEO_CARDS=i965 > > Thanks for the explanation Right, but people set USE="gallium classic vdpau" VIDEO_CARDS="i965" and then don't understand why they don't have VDPAU :) (The answer is that i965 is not a gallium driver, and the VDPAU support code in Mesa is gallium-only) Ah, in that case I would opt for showing and ewarn message explaining that XX support is skipped due to incompatible USE flags or explaining the situation a bit. That has also the advantage of teaching people that peculiarities and help us to understand the situation ;) Then... can we go for allowing people wanting opencl support to enable it globally and get things working by default even showing warnings? ;) Thanks a lot :) Any news on this? Thanks My USE flags for mesa used to be "X classic dri3 egl gallium gbm gles2 llvm vaapi xa -d3d9 -debug -gles1 (-libglvnd) -lm-sensors -opencl -osmesa -pax_kernel (-selinux) -test -unwind -valgrind -vdpau -vulkan -vulkan-overlay -wayland -xvmc" up until now when the ebuild forces me to enable opencl as well. Because I'm on intel gfx this change brought me here... I don't understand most of these USE flags and didn't change any of them willingly (only because emerge told me to do so), so what should I do? What is current state of bug? Does it fixed? Is there any news on this, please? This is no longer an issue as rusticl supports Intel GPUs. |