From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: Sarah Morgensen <iskarian@mgsn.dev>, 50418-done@debbugs.gnu.org
Subject: bug#50418: [PATCH core-updates-frozen 0/2] gnu: ocl-icd: Fix build.
Date: Tue, 12 Oct 2021 14:37:44 -0400 [thread overview]
Message-ID: <878ryyytqf.fsf_-_@gmail.com> (raw)
In-Reply-To: <YTjQRS3/rPdeYrj4@noor.fritz.box> (Lars-Dominik Braun's message of "Wed, 8 Sep 2021 17:01:25 +0200")
Hi,
Lars-Dominik Braun <lars@6xq.net> writes:
> Hi Sarah,
>
>> Is the Khronos Group one better, such that there's no reason to keeping
>> ocl-icd? (The README for ocl-icd states "[t]his package aims at
>> creating an Open Source alternative to vendor specific OpenCL ICD
>> loaders." Is the Khronos Group one similarly not vendor-specific?)
> I’m not really sure which one is “better”, but the Khronos-loader
> is vendor-independent like ocl-icd, so there’s no real reason to
> keep two imho.
>
>> If so, would you consider replacing ocl-icd with it in
>> core-updates-frozen, since it and its dependents are currently broken?
> Ludovic actually merged master into core-updates-frozen yesterday, so
> this issue should be resolved. Unfortunately the CI is going to take
> some time to catch up, so we don’t know yet whether that was successful.
>
> Cheers,
> Lars
Since we already have opencl-icd-loader deprecating ocl-icd in the
frozen branch (see commit 4d1157fca7), let's drop this change for now.
Thank you,
Closing.
Maxim
prev parent reply other threads:[~2021-10-12 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 2:46 [bug#50418] [PATCH core-updates-frozen 0/2] gnu: ocl-icd: Fix build Sarah Morgensen
2021-09-06 2:49 ` [bug#50418] [PATCH core-updates-frozen 1/2] gnu: ocl-icd: Update project location Sarah Morgensen
2021-09-06 2:49 ` [bug#50418] [PATCH core-updates-frozen 2/2] gnu: ocl-icd: Update to 2.2.13 Sarah Morgensen
2021-09-06 5:57 ` [bug#50418] [PATCH core-updates-frozen 0/2] gnu: ocl-icd: Fix build Lars-Dominik Braun
2021-09-06 17:20 ` Sarah Morgensen
2021-09-08 15:01 ` Lars-Dominik Braun
2021-10-12 18:37 ` Maxim Cournoyer [this message]
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=878ryyytqf.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=50418-done@debbugs.gnu.org \
--cc=iskarian@mgsn.dev \
--cc=lars@6xq.net \
/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).