| 1 |
Dear everyone, |
| 2 |
|
| 3 |
I am happy to say that we are now almost ready for switching to |
| 4 |
eselect-opencl-free handling of OpenCL in Gentoo. Both ocl-icd and |
| 5 |
opencl-icd-loader have now got (masked) versions in the tree which |
| 6 |
install directly into /usr, the switching between the two works |
| 7 |
seamlessly, and I have yet to see any OpenCL-aware package - OpenCL |
| 8 |
runtimes included - which fails to build in this configuration, |
| 9 |
regardless of which of the two loaders is used. |
| 10 |
|
| 11 |
As far as I can see, there are only two things left to do: |
| 12 |
|
| 13 |
1. Migrate x11-drivers/nvidia-drivers to the new approach. This is a |
| 14 |
major one because with >=virtual/opencl-3 no longer depending on any |
| 15 |
runtimes and the adapted incarnations of both ICD loaders block |
| 16 |
eselect-opencl in order to avoid file collisions, unmasking the latter |
| 17 |
right now would effectively kill OpenCL support for Nvidia users. I have |
| 18 |
just opened a ticket regarding this: |
| 19 |
|
| 20 |
https://bugs.gentoo.org/717042 |
| 21 |
|
| 22 |
Perhaps fast-tracking stabilisation of the latest version of |
| 23 |
virtual/opencl might help too? |
| 24 |
|
| 25 |
|
| 26 |
2. On systems with FEATURES=collision-protect set it will be necessary |
| 27 |
to manually clean up the libOpenCL.so symlinks created by |
| 28 |
eselect-opencl, before starting an upgrade - those symlinks are *not* |
| 29 |
owned by eselect-opencl as far as Portage is concerned so neither the |
| 30 |
standard weak-blocker resolution nor uninstalling this package prior to |
| 31 |
the upgrade prevent file collisions. I will prepare a news item |
| 32 |
(attached to eselect-opencl) explaining this soon. |
| 33 |
|
| 34 |
|
| 35 |
Again, many thanks to everyone who has contributed to making this happen! |
| 36 |
|
| 37 |
-- |
| 38 |
Marecki |
Archives