[Bug 1173005] Get rid of system config files in /etc: Mesa
http://bugzilla.opensuse.org/show_bug.cgi?id=1173005 http://bugzilla.opensuse.org/show_bug.cgi?id=1173005#c10 --- Comment #10 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Sergey Kondakov from comment #9)
POCL is in the distribution, Its package just not seem to be updated well.
Ok. I can do a submit request to adjust the location for the .icd file for pocl.
And that actual implementations of OpenCL (you know, the things it was created for) are not in the distribution is a deficiency in the distribution. Unless you package libOpenCL for pure pedantry and not for it to actually work and be useful in offloading GPU-specific computing on a GPU.
And then what is what we have in Mesa-libOpenCL package?
If you going to put things in unobvious places then you may want to notify upstream of that at https://github.com/OCL-dev/ocl-icd/issues/7
Hmm. Then we would need to set an env. variable by default via /etc/profile.d. But since you're an expert in this area. Can you explain to me, which .icd file is being used if more than one is being found?
Not sure why you even use it instead of https://github.com/KhronosGroup/OpenCL-ICD-Loader
Well, I'm not the maintainer of the libOpenCL package at all. I'm only maintaining the Mesa package and needed to move the .icd file, so I changed libOpenCL package accordingly. I haven't created ocl-icd package either. Also it seems ocl-icd package has been created before the Kronos group released their opencl-icd loader and nobody noticed about the Khronos implementation. Probably it would make sense to switch to that one.
I kludged-up my packages and not going to go through official hoops.
Hmm. Not sure what you meant to say here exactly.
By the way, Mesa package is currently missing SPIRV-Tools & LLVMSPIRVLib (which is also dependency of intel-compute) and you might want to enable gallium-based osmesa, lmsensors support in GALLIUM_HUD and swr, now that it seem to be fixed to no longer break Mesa on non-avx CPUs due to static linking and unwanted initialization.
This sounds unrelated. Could you please open a separate Mesa ticket for this, please? You can assign it directly to me. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com