Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 699436 - media-libs/mesa[opencl] blocks intel users
Summary: media-libs/mesa[opencl] blocks intel users
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal with 3 votes (vote)
Assignee: Gentoo X packagers
Depends on:
Reported: 2019-11-06 10:17 UTC by Pacho Ramos
Modified: 2020-12-23 11:55 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Pacho Ramos gentoo-dev 2019-11-06 10:17:14 UTC
I was wondering about enabling opencl in gromacs and, supposedly, it should work on my intel setup. Then I realized about simply enabling opencl globally to allow other apps to benefit from this. The problem is that this leads to blocks as mesa[opencl] tries to pull in a package (dev-libs/libclc) that forces to have either r600, radeonsi or nvidia cards. This is normal as it seems mesa opengl is for this cards, while intel users rely on beignet or compute-runtime (bug 648258).

I wonder then about why mesa[opencl] USE flag is put behind the video_cards_* that support it to not cause this blocks for people using other cards, allowing to simply enable opencl and get it working with the proper implementation for all the devices. 

Comment 1 Matt Turner gentoo-dev 2019-11-17 22:44:59 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.
Comment 2 Pacho Ramos gentoo-dev 2019-11-17 22:52:04 UTC
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
Comment 3 Matt Turner gentoo-dev 2019-11-18 05:19:08 UTC
(In reply to Pacho Ramos from comment #2)
> I don't understand the issue with that gallium-only USEs and i965 in
> 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)
Comment 4 Pacho Ramos gentoo-dev 2019-11-18 17:21:33 UTC
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 ;)
Comment 5 Pacho Ramos gentoo-dev 2019-12-05 07:33:22 UTC
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 :)
Comment 6 Pacho Ramos gentoo-dev 2019-12-15 19:33:33 UTC
Any news on this? Thanks
Comment 7 Timo Ollech 2020-02-26 20:07:09 UTC
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?
Comment 8 Reva Denis 2020-12-23 11:55:49 UTC
What is current state of bug? Does it fixed?