From: Guillaume Le Vaillant <glv@posteo.net>
To: 66072@debbugs.gnu.org
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, Lars-Dominik Braun <lars@6xq.net>
Subject: bug#66072: Duplicate/conflicting definitions for ocl-icd
Date: Mon, 18 Sep 2023 12:34:57 +0000 [thread overview]
Message-ID: <87ttrrslet.fsf@kitej> (raw)
[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]
Hi.
There are currently two conflicting definitions of ocl-icd in
"opencl.scm":
--8<---------------cut here---------------start------------->8---
(define-public ocl-icd
(deprecated-package "ocl-icd" opencl-icd-loader))
--8<---------------cut here---------------end--------------->8---
and
--8<---------------cut here---------------start------------->8---
(define-public ocl-icd
(package
(name "ocl-icd")
(version "2.3.2")
(source
(origin
(method git-fetch)
(uri (git-reference
(url "https://github.com/OCL-dev/ocl-icd")
(commit (string-append "v" version))))
(file-name (git-file-name name version))
(sha256
(base32 "0y0lnxb6zlhfb5vxxib5n1vvxa4b23qc0j3lsih6yjz9j37mj7wz"))))
(build-system gnu-build-system)
(native-inputs
(list autoconf automake libtool ruby))
(home-page "https://github.com/OCL-dev/ocl-icd")
(synopsis "Generic OpenCL @acronym{ICD, Installable Client Driver} loader")
(description
"This package provides an OpenCL @acronym{ICD, Installable Client Driver}
loader. It maintains a YAML database of all known and guessed function pointers
from vendor-specific drivers. It also delivers a skeleton of bindings to
incorporate inside an OpenCL implementation to give it ICD functionalities.")
(license license:bsd-2)))
--8<---------------cut here---------------end--------------->8---
Which is the good one?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next reply other threads:[~2023-09-18 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 12:34 Guillaume Le Vaillant [this message]
2023-09-18 14:23 ` bug#66072: Duplicate/conflicting definitions for ocl-icd Lars-Dominik Braun
2023-09-18 17:57 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-09-21 15:44 ` Guillaume Le Vaillant
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttrrslet.fsf@kitej \
--to=glv@posteo.net \
--cc=66072@debbugs.gnu.org \
--cc=lars@6xq.net \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).