From: ifreund <ifreund@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC]: decouple zig and llvm packages
Date: Mon, 02 May 2022 17:36:56 +0200 [thread overview]
Message-ID: <20220502153656.0pOrDE0GIsjPrP4RUYrBad3Mp_tZgxa3kE9z-yVoTL4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36951@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
New comment by ifreund on void-packages repository
https://github.com/void-linux/void-packages/issues/36951#issuecomment-1115044325
Comment:
> Because it's been blocking the update #36229 #34800 for 4 months and is arguably not very useful (2 packages).
zig isn't blocking llvm 13, I sent patches for the zig related things many months ago. The only thing blocking llvm 13 as far as I'm aware is someone with void-packages commit access to find time to review and merge the PR.
I did comment in one of those threads that zig is not compatible with llvm 14 yet and won't be for the next month or so at least. That does not block llvm 13 being merged though.
Zig does not require any patches to llvm or otherwise make it difficult to use a system llvm installation of the proper version. If we need llvm 14 before zig 0.10.0 is released then I recommend doing as duncaen says and keeping a llvm13 package around until zig 0.10.0 is released.
The root cause of this problem is that each llvm release is incompatible with the last and that llvm is a very large and expensive dependency to build from source.
next prev parent reply other threads:[~2022-05-02 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 10:32 [ISSUE] " prez
2022-05-02 13:42 ` Duncaen
2022-05-02 14:56 ` prez
2022-05-02 14:56 ` prez
2022-05-02 15:36 ` ifreund [this message]
2022-05-02 20:45 ` prez
2022-05-02 20:48 ` Duncaen
2022-05-02 20:59 ` [ISSUE] [CLOSED] " prez
2022-05-02 20:59 ` prez
2022-05-02 21:03 ` Duncaen
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=20220502153656.0pOrDE0GIsjPrP4RUYrBad3Mp_tZgxa3kE9z-yVoTL4@z \
--to=ifreund@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).