On Mon, Sep 11, 2023 at 2:37 AM Timothy Pearson <tpear...@raptorengineering.com> wrote: > > For 16 to work we'll need the Debian clang team to include this patchset: > > https://reviews.llvm.org/D158066 > > Any chance of that happening? > > ----- Original Message ----- > > From: "Andres Salomon" <dilin...@queued.net> > > To: "Leandro Cunha" <leandrocunha...@gmail.com>, 1051...@bugs.debian.org > > Cc: "Timothy Pearson" <tpear...@raptorengineering.com> > > Sent: Sunday, September 10, 2023 11:43:18 PM > > Subject: Re: Bug#1051355: Processed: your mail > > > Alright, I built 117 w/ clang-16 on sid and it doesn't segfault. Same > > exact build but with clang-14 segfaults. > > > > Timothy, did you ever get the ppc64 issues with clang >= 15 squared > > away? It's looking like I'm going to need to upload a build with > > clang-16. > > > > On Sun, Sep 10 2023 at 03:07:29 PM -03:00:00, Leandro Cunha > > <leandrocunha...@gmail.com> wrote: > >> Hi, > >> > >> Em dom., 10 de set. de 2023 15:01, Andres Salomon > >> <dilin...@queued.net <mailto:dilin...@queued.net>> escreveu: > >>> Unfortunately 117 *also* segfaults on sid. > >>> > >>> I'm tempted to try a newer clang, but probably not 15 since debian's > >>> planning to remove it. 16, I guess? > >> > >> Arch is already with Clang 16 and I tested Chromium 117 in a vm that > >> I installed here and it was working normally.
Clang migration will have to go through a transition, as it may still break some packages and this requires care. Which could still delay the release of new versions of Chromium. Example: https://lists.debian.org/debian-release/2019/12/msg00402.html -- Cheers, Leandro Cunha
