From: Alyssa Ross <hi@alyssa.is>
To: distributions@lists.linux.dev
Cc: primeos <dev.primeos@gmail.com>, Ryan Lahfa <ryan@lahfa.xyz>,
Lorenz Brun <lorenz@brun.one>
Subject: Next Chromium release will require unreleased LLVM
Date: Thu, 11 May 2023 09:27:45 +0000 [thread overview]
Message-ID: <20230511092745.l53qykvz7roq4dqj@x220> (raw)
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
The Chromium 114 beta uses features from LLVM 17, but will release
before LLVM 17 does. Currently, it looks like it wouldn't be too hard
to patch to make it compatible with LLVM 16, but in general, we don't
have any guarantee that Chromium will build with a released LLVM.
So, how do you intend to handle this situation in your distribution?
It seems like it will be a problem we'll all share, especially if it
gets worse in future.
Nixpkgs discussion:
https://github.com/NixOS/nixpkgs/issues/213862#issuecomment-1542887001
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-05-11 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 9:27 Alyssa Ross [this message]
2023-05-11 10:16 ` Next Chromium release will require unreleased LLVM Neal Gompa
2023-05-11 11:35 ` Ryan Lahfa
2023-05-11 11:43 ` Alyssa Ross
2023-05-12 7:20 ` alice
2023-05-14 19:05 ` Ryan Lahfa
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=20230511092745.l53qykvz7roq4dqj@x220 \
--to=hi@alyssa.is \
--cc=dev.primeos@gmail.com \
--cc=distributions@lists.linux.dev \
--cc=lorenz@brun.one \
--cc=ryan@lahfa.xyz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).