On Mon, Sep 11, 2023 at 4:10 PM Andres Salomon <dilin...@queued.net> wrote: > > > > On Mon, Sep 11 2023 at 03:27:30 PM -03:00:00, Leandro Cunha > <leandrocunha...@gmail.com> wrote: > > On Mon, Sep 11, 2023 at 4:07 AM Andres Salomon <dilin...@queued.net> wrote: > > So apparently it's already fixed in sid and trixie: > https://tracker.debian.org/news/1454349/accepted-llvm-toolchain-16-11606-11-source-into-unstable/ > Bug didn't get closed because of the missing "(closes: " in that changelog > entry. I'll push the clang-16 stuff to git so you can give it a test build on > ppc. On Mon, Sep 11 2023 at 12:37:39 AM -05:00:00, 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. > > So we already have this version on unstable? I saw it in experimental. > https://metadata.ftp-master.debian.org/changelogs//main/l/llvm-defaults/llvm-defaults_0.57~exp4_changelog > > > That's just the defaults package, which we don't really care about. Because > we're dealing with different compilers across different distributions, we're > hardcoding the specific clang version for each distribution's build.
Ah yes, I see, there is a user on GitHub who compiles Chromium for Ubuntu, Debian and Windows operating systems with Clang/LLVM. I also tested the .deb package it offers in version 117 and it worked. But of course I had to delete the package distributed by Debian. And I also didn't find any segmentation fault bug reports in version 116 in my search. In this sense, research was carried out on other distributions and their bug tracker. But I noticed that this problem sometimes occurs considering the links inserted here. https://groups.google.com/a/chromium.org/g/chromium-bugs/search?q=segmentation%20fault https://bugs.chromium.org/p/chromium/issues/detail?id=48168 https://bbs.archlinux.org/viewtopic.php?id=151904 https://bugs.chromium.org/p/chromium/issues/list?q=segmentation%20fault&can=2 https://groups.google.com/a/chromium.org/g/chromium-bugs/c/wolJA_Ma4ZE https://github.com/RobRich999/Chromium_Clang -- Cheers, Leandro Cunha
