From: Brian Evans <grknight@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] News item: manual steps required to transition from eselect-opencl to direct icd-loader use
Date: Sat, 11 Apr 2020 09:54:20 -0400 [thread overview]
Message-ID: <4508ba80-8f44-f6c7-fe90-c50a23a21e45@gentoo.org> (raw)
In-Reply-To: <47aeae14-243d-9803-6570-f051a42ba50a@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1753 bytes --]
On 4/11/20 9:37 AM, Marek Szuba wrote:
> Does this look okay to you, guys? The date is preliminary and dependent
> on how quickly we can get nvidia-drivers migrated to the new approach,
> hopefully we can get this to happen sooner.
>
> * * *
>
> Title: Manual steps required during upgrade to an eselect-free OpenCL set-up
> Author: Marek Szuba <marecki@gentoo.org>
> Posted: 2020-05-01
> Revision: 1
> News-Item-Format: 2.0
> Display-If-Installed: app-eselect/eselect-opencl
>
> We are now in the process of migrating OpenCL in Gentoo to having all
> implementations operate through an ICD loader (dev-libs/ocl-icd or
> dev-libs/opencl-icd-loader) installed directly into /usr instead of
> using eselect-opencl to switch between implementations. eselect-free
> versions
> of loader packages have just been released to the public.
>
> Unfortunately although the upgrade to those versions will automatically
> uninstall app-eselect/eselect-opencl, it will not remove the symbolic
> links to
> libOpenCL.so created by this tool in library directories because those links
> are not owned by the package in question. If your system is configured for
> full collision protection (FEATURES=collision-protect), it will be necessary
> to manually remove those links
>
> rm -i /usr/lib{,64}/libOpenCL.so*
>
> before running the upgrade.
>
> Systems whose collision protection either allows overwriting orphaned files
> (FEATURES='-collision-protect protect-owned') or which do not use collision
> protection at all (not recommended) should be unaffected.
>
>
>
I would mention that FEATURES='-collision-protect protect-owned' is the
default so most people won't have any action to take at all.
Brian
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2020-04-11 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 13:37 [gentoo-dev] News item: manual steps required to transition from eselect-opencl to direct icd-loader use Marek Szuba
2020-04-11 13:54 ` Brian Evans [this message]
2020-04-11 16:04 ` Ulrich Mueller
2020-04-11 17:32 ` Marek Szuba
2020-04-11 19:28 ` Ulrich Mueller
2020-04-11 21:54 ` [gentoo-dev] News item v2: potential file collisions during OpenCL upgrade Marek Szuba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4508ba80-8f44-f6c7-fe90-c50a23a21e45@gentoo.org \
--to=grknight@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox