commit:     0bf1115193ab82db31e31e684938d9c2b1749308
Author:     David Seifert <soap <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 20 10:57:39 2021 +0000
Commit:     David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Mon Dec 20 10:57:39 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0bf11151

profiles: last-rite CUDA 10

Closes: https://github.com/gentoo/gentoo/pull/23425
Bug: https://bugs.gentoo.org/721808
Bug: https://bugs.gentoo.org/760708
Signed-off-by: David Seifert <soap <AT> gentoo.org>

 profiles/base/package.use.mask | 6 ++++++
 profiles/package.mask          | 7 +++++++
 2 files changed, 13 insertions(+)

diff --git a/profiles/base/package.use.mask b/profiles/base/package.use.mask
index b4b7b45fa8f0..7cd1f91b55eb 100644
--- a/profiles/base/package.use.mask
+++ b/profiles/base/package.use.mask
@@ -6,6 +6,12 @@
 # This file is only for generic masks. For arch-specific masks (i.e.
 # mask everywhere, unmask on arch/*) use arch/base.
 
+# David Seifert <[email protected]> (2021-12-19)
+# Requires GCC 8, security vulnerabilities, switch to CUDA 11,
+# consider using clang+NVPTX backend for sm_30 cards.
+# Removal in 90 days, bug #721808, #760708.
+dev-libs/cudnn cuda10-2
+
 # Thomas Deutschmann <[email protected]> (2021-12-03)
 # Requires newer media-libs/dav1d which isn't available yet,
 # see https://bugzilla.mozilla.org/1734058

diff --git a/profiles/package.mask b/profiles/package.mask
index e5bdca55d285..a594fb75eca1 100644
--- a/profiles/package.mask
+++ b/profiles/package.mask
@@ -33,6 +33,13 @@
 
 #--- END OF EXAMPLES ---
 
+# David Seifert <[email protected]> (2021-12-20)
+# Requires GCC 8, security vulnerabilities, switch to CUDA 11,
+# consider using clang+NVPTX backend for sm_30 cards.
+# Removal in 90 days, bug #721808, #760708.
+<dev-util/nvidia-cuda-sdk-11
+<dev-util/nvidia-cuda-toolkit-11
+
 # Michał Górny <[email protected]> (2021-12-20)
 # Switches from deprecated stdlib distutils to vendored distutils
 # by default.  Masked for testing.  See tracker bug #822354.

Reply via email to