Re: Next Chromium release will require unreleased LLVM
Ryan Lahfa <[email protected]> Thu, 11 May 2023 13:35:48 +0200
| Newsgroups | dev.linux.lists.distributions |
|---|---|
| Message-ID | <fyojmpiizynnkvvqqwarfubob6vs5xvdi3wpegtgw4ofpksc4v@oldvvj4faghd> |
On Thu, May 11, 2023 at 06:16:03AM -0400, Neal Gompa wrote: > On Thu, May 11, 2023 at 5:27 AM Alyssa Ross <[email protected]> wrote: > > > > 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 > > I suspect we in Fedora will do the same thing and revert/modify things > to work with LLVM/Clang 16. It is, however, not out of the question > for us to ship multiple versions of LLVM+Clang in Fedora, so once LLVM > 17 is shipped in Fedora, we will probably switch Chromium to that. We already do the same in nixpkgs (from LLV5 to LLVM16 at the moment, but hopefully, we start dropping the oldest ones). > We only recently switched building Chromium from GCC to Clang. > Switching back might be an option too, depending on what the > compatibility looks like. I thought that Chromium was tightly coupled to Clang for compilation. > I'm personally not a fan of the Clang/LLVM toolchain after having > worked on building distributions entirely using it before. But alas, > I'm in the minority. :/ Curious about your pain points, but, probably off-topic. :) Kind regards, -- Ryan Lahfa