public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Paul Zander" <negril.nx+gentoo@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: sci-misc/llama-cpp/
Date: Tue, 22 Jul 2025 18:44:19 +0000 (UTC)	[thread overview]
Message-ID: <1753208730.451623c534e7e4fa47a2793c85f5f4fbabc518c6.negril.nx+gentoo@gentoo> (raw)

commit:     451623c534e7e4fa47a2793c85f5f4fbabc518c6
Author:     Paul Zander <negril.nx+gentoo <AT> gmail <DOT> com>
AuthorDate: Tue Jul 22 17:55:49 2025 +0000
Commit:     Paul Zander <negril.nx+gentoo <AT> gmail <DOT> com>
CommitDate: Tue Jul 22 18:25:30 2025 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=451623c5

sci-misc/llama-cpp: set CUDAHOSTCXX via cuda.eclass

Closes: https://bugs.gentoo.org/960549
Signed-off-by: Paul Zander <negril.nx+gentoo <AT> gmail.com>

 sci-misc/llama-cpp/llama-cpp-0_pre5857.ebuild | 7 +++++++
 sci-misc/llama-cpp/llama-cpp-9999.ebuild      | 7 +++++++
 2 files changed, 14 insertions(+)

diff --git a/sci-misc/llama-cpp/llama-cpp-0_pre5857.ebuild b/sci-misc/llama-cpp/llama-cpp-0_pre5857.ebuild
index 3c299357c9..3f39aebf74 100644
--- a/sci-misc/llama-cpp/llama-cpp-0_pre5857.ebuild
+++ b/sci-misc/llama-cpp/llama-cpp-0_pre5857.ebuild
@@ -93,6 +93,13 @@ src_configure() {
 		)
 	fi
 
+	if use cuda; then
+		local -x CUDAHOSTCXX="$(cuda_gccdir)"
+		# tries to recreate dev symlinks
+		cuda_add_sandbox
+		addpredict "/dev/char/"
+	fi
+
 	if use hip; then
 		rocm_use_hipcc
 		mycmakeargs+=(

diff --git a/sci-misc/llama-cpp/llama-cpp-9999.ebuild b/sci-misc/llama-cpp/llama-cpp-9999.ebuild
index 3c299357c9..3f39aebf74 100644
--- a/sci-misc/llama-cpp/llama-cpp-9999.ebuild
+++ b/sci-misc/llama-cpp/llama-cpp-9999.ebuild
@@ -93,6 +93,13 @@ src_configure() {
 		)
 	fi
 
+	if use cuda; then
+		local -x CUDAHOSTCXX="$(cuda_gccdir)"
+		# tries to recreate dev symlinks
+		cuda_add_sandbox
+		addpredict "/dev/char/"
+	fi
+
 	if use hip; then
 		rocm_use_hipcc
 		mycmakeargs+=(


             reply	other threads:[~2025-07-22 18:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 18:44 Paul Zander [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-08  2:12 [gentoo-commits] repo/proj/guru:dev commit in: sci-misc/llama-cpp/ Sergey Alirzaev
2025-09-12  0:41 Sergey Alirzaev
2025-08-29 16:25 Sergey Alirzaev
2025-08-12 21:39 Sergey Alirzaev
2025-08-10  0:37 Sergey Alirzaev
2025-08-05 20:26 Sergey Alirzaev
2025-07-31 15:04 Sergey Alirzaev
2025-07-27 22:59 Sergey Alirzaev
2025-07-23 23:36 David Roman
2025-07-23 12:49 Piotr Kubaj
2025-07-10  0:16 Sergey Alirzaev
2025-07-04  2:17 Sergey Alirzaev
2025-07-03 22:22 Sergey Alirzaev
2025-07-03 19:33 Sergey Alirzaev
2025-06-11 12:53 Sergey Alirzaev
2025-05-17 12:57 Sergey Alirzaev
2025-05-09 23:39 Sergey Alirzaev
2025-04-10 19:52 Sergey Alirzaev
2025-03-07 11:16 Sergey Alirzaev
2025-02-23 17:54 Sergey Alirzaev
2025-02-20 14:58 Sergey Alirzaev
2025-02-08 16:59 Alexey Korepanov
2025-02-01 11:21 Sergey Alirzaev
2025-01-29  0:14 Sergey Alirzaev
2025-01-29  0:11 Sergey Alirzaev
2025-01-27 15:10 Takuya Wakazono
2025-01-27 11:52 Sergey Alirzaev

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=1753208730.451623c534e7e4fa47a2793c85f5f4fbabc518c6.negril.nx+gentoo@gentoo \
    --to=negril.nx+gentoo@gmail.com \
    --cc=gentoo-commits@lists.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