Github messages for voidlinux
 help / color / mirror / Atom feed
From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libclc: rename from libclc-git and update to 11.0.0
Date: Tue, 24 Nov 2020 18:47:12 +0100	[thread overview]
Message-ID: <20201124174712.CJe30OyGw9y1BSfM1Aqi-43PvFe7PoSoB5mjvl7qgpY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26580@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 496 bytes --]

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/pull/26580#issuecomment-733136166

Comment:
Hmm, and I have no idea how to test it. Nothing depends on `mesa-opencl`.
I have a Radeon RX 550 (Baffin) and believe it is not among the supported hardware,
at least there is no `usr/share/clc/baffin-*--.bc` file in `libclc-11.0.1_1.x86_64.xbps`.
Probably needs a real R600 card to test with. But then why shouldn't it work if it compiles w/o issues?

  parent reply	other threads:[~2020-11-24 17:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21 22:12 [PR PATCH] " pullmoll
2020-11-21 22:15 ` [PR PATCH] [Updated] " pullmoll
2020-11-21 22:24 ` pullmoll
2020-11-22 18:49 ` [PR PATCH] [Updated] " pullmoll
2020-11-22 18:59 ` pullmoll
2020-11-22 19:01 ` pullmoll
2020-11-22 19:03 ` [PR PATCH] [Updated] " pullmoll
2020-11-22 19:07 ` pullmoll
2020-11-22 19:16 ` [PR REVIEW] " ericonr
2020-11-22 19:20 ` pullmoll
2020-11-22 19:23 ` pullmoll
2020-11-22 19:24 ` pullmoll
2020-11-22 19:27 ` pullmoll
2020-11-22 19:38 ` [PR PATCH] [Updated] " pullmoll
2020-11-24 17:47 ` pullmoll [this message]
2020-11-25 12:31 ` pullmoll
2020-11-25 18:49 ` [PR REVIEW] " Vaelatern
2020-11-25 19:04 ` pullmoll
2020-11-25 19:18 ` Vaelatern
2020-11-25 19:32 ` pullmoll
2020-11-25 19:36 ` [PR PATCH] [Updated] " pullmoll
2020-11-25 19:37 ` pullmoll
2020-11-25 20:07 ` pullmoll

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=20201124174712.CJe30OyGw9y1BSfM1Aqi-43PvFe7PoSoB5mjvl7qgpY@z \
    --to=pullmoll@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).