From: Calandracas606 <Calandracas606@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: llvm18
Date: Sat, 06 Apr 2024 03:37:08 +0200 [thread overview]
Message-ID: <20240406013708.778832960E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48661@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
New comment by Calandracas606 on void-packages repository
https://github.com/void-linux/void-packages/pull/48661#issuecomment-2040847876
Comment:
> I saw this while checking on where zig was at. I have [intel opencl](https://github.com/void-linux/void-packages/pull/43084) that was working with llvm15 but from intel's open issues 16, and I assume 17, will be in the air for a while. With 18 being updated, should I just mark intel opencl as a lost cause? I don't know that they will ever be "caught up" and things will be able to compile with void's versions.
llvm15 won't be going anywhere. the libraries (libllvm15, libclang15, etc) will likely stick around as long as they are needed, llvm12 is still packaged for example
next prev parent reply other threads:[~2024-04-06 1:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 22:16 [PR PATCH] " Calandracas606
2024-02-12 2:16 ` [PR PATCH] [Updated] " Calandracas606
2024-02-12 3:02 ` Calandracas606
2024-02-12 3:18 ` Calandracas606
2024-02-12 15:56 ` Calandracas606
2024-02-15 11:51 ` [PR REVIEW] " sgn
2024-02-15 11:51 ` sgn
2024-02-15 11:52 ` sgn
2024-03-13 14:53 ` [PR PATCH] [Updated] " Calandracas606
2024-03-13 16:49 ` Calandracas606
2024-04-02 14:50 ` Calandracas606
2024-04-02 15:52 ` Calandracas606
2024-04-06 0:24 ` zlice
2024-04-06 1:37 ` Calandracas606 [this message]
2024-04-06 1:41 ` zlice
2024-04-06 13:23 ` zlice
2024-04-10 15:00 ` leahneukirchen
2024-04-10 17:11 ` Calandracas606
2024-04-11 2:48 ` Calandracas606
2024-04-18 14:29 ` Calandracas606
2024-04-18 14:40 ` [PR PATCH] [Updated] " Calandracas606
2024-04-18 14:42 ` Calandracas606
2024-04-18 14:55 ` Calandracas606
2024-04-18 15:07 ` [PR PATCH] [Updated] " Calandracas606
2024-04-18 15:54 ` Calandracas606
2024-04-18 21:08 ` Calandracas606
2024-04-18 21:52 ` Calandracas606
2024-04-22 22:28 ` [PR PATCH] [Updated] " Calandracas606
2024-04-23 3:12 ` Calandracas606
2024-04-29 2:54 ` Calandracas606
2024-04-29 2:55 ` Calandracas606
2024-04-29 21:58 ` Calandracas606
2024-05-01 12:41 ` Calandracas606
2024-05-01 13:05 ` Calandracas606
2024-05-03 15:04 ` Calandracas606
2024-05-04 3:08 ` Calandracas606
2024-05-17 20:45 ` Calandracas606
2024-05-29 13:21 ` Calandracas606
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=20240406013708.778832960E@inbox.vuxu.org \
--to=calandracas606@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).