Created attachment 908906 [details] emerge --info chromium Getting a mysterious (to me) compile error when upgrading to chromium-132.
Created attachment 908907 [details] partial build log The build.log is 188M, even gzipped is 3.5M which is too big to attach. I have put instead "tail --lines=50".
Looks like this is an LLVM19+ feature: https://github.com/llvm/llvm-project/issues/106839
../../pdf/pdfium/pdfium_api_wrappers.cc:150:32: error: alias template 'PDFiumAPIStringBufferAdapter' requires template arguments; argument deduction only allowed for class templates 150 | PDFiumAPIStringBufferAdapter adapter(&name, expected_size, | ^ ../../pdf/pdfium/pdfium_api_string_buffer_adapter.h:173:1: note: template is declared here 173 | using PDFiumAPIStringBufferAdapter = | ^ 1 error generated.
I attempted the install again today, it fell over with the same error.
Yes, I have not yet looked into this, but it will likely require a new patch - stay tuned. I am not hitting it with either llvm 18 or 19 in testing. As a workaround until I patch the ebuild, you could try setting `USE="-llvm_slot_18 llvm_slot_19" which should use a later llvm that will work with this code.
It's trying to rebuild media-libs/mesa which is blocked on LLVM_SLOT. I'll look into it tomorrow.
I didn't realize 132 is masked. I've been looking into https://bugs.gentoo.org/942844 thinking a later version of chromium might not have the problem, however it's looking like a pulseaudio bug, although I'm having a tough time proving it. You could just close this one.
132 is keyworded ~arch on amd64 and arm64 - It's supposed to be available for users who wish to opt-in. The 'beta' subslot will never be keyworded stable for those arches. You can select the '0/stable' subslot if you never wish to opt into beta releases but would like to see earlier stable channel packages. 133 (current 'dev' channel) is not keyworded, and dev channel releases (at this time) will never be keyworded; that's reserved for beta. There's nothing wrong with using the dev channel - upstream's CI is "pretty good"
It sounds like we're going to stablereq llvm/clang 19 and drop clang 18 for Chromium; the change that causes this is non-trivial to revert / do in a way that clang18 will tolerate.
And that's done - profiles should be on 19 by now. I'll make sure 18 is dropped from ebuilds over the next week or so.
