| Summary: | www-client/chromium-122.0.6261.6[system-toolchain] fails to build | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
| Component: | Current packages | Assignee: | Chromium Project <chromium> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ben, gem, juippis, kangie, kvaster, mail, volkov |
| Priority: | Normal | Keywords: | PATCH, PullRequest |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://github.com/gentoo/gentoo/pull/35122 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build log
ebuild patch build log (122.0.6261.6-r1) |
||
|
Description
Patrick Lauer
2024-01-27 14:39:04 UTC
Full build.log please. Created attachment 883642 [details]
build log
I hit the same problem with dev-lang/rust-1.74.1. Adding RUSTC_BOOTSTRAP=1 to the ebuild made www-client/chromium-122.0.6261.6[system-toolchain] build successfully, see the attached example. Created attachment 883655 [details, diff]
ebuild patch
Maciej, how is your system rust built? Are you using `USE=system-llvm`? I haven't hit this yet, but I'm trying to repro. Patch fixes problem for me. At my setup I'm using only: 'lto profiler' for rust. No 'system-llvm'. > Maciej, how is your system rust built? Are you using `USE=system-llvm`? > dev-lang/rust-1.74.1:stable/1.74::gentoo USE="lto profiler system-llvm" (rest of USE flags are disabled) I don't think it's system-llvm related though - it's well known that stable Rust compiler versions don't allow "Z" options without RUSTC_BOOTSTRAP. > it's well known that stable Rust compiler versions don't allow "Z" options without RUSTC_BOOTSTRAP.
And yet I can't reproduce this issue on multiple machines. Something is weird here (We did hit this during 121 stablisation though, so it's definitely real).
Could you please try with the new 121 release, 121.0.6167.139, or with 122.0.6261.6-r1 and let me know if you still hit the issue? I tidied up a lot of the system-toolchain/google-toolchain stuff over the last week.
It's entirely possible that in some of the USE=`system-toolchain` shuffling I missed a step that would set that envvar as part of the GN build. If it's still not working I'll dig deep into GN over the weekend and see what I can work out - I'm loathe to cargo cult an additional rust variable rather than work out why this is (seemingly?) working on most machines.
> Could you please try with the new 121 release, 121.0.6167.139, or with 122.0.6261.6-r1 and let me know if you still hit the issue?
I am also affected and I just tried 122.0.6261.6-r1 and still hit the issue.
Created attachment 883862 [details]
build log (122.0.6261.6-r1)
*** Bug 923265 has been marked as a duplicate of this bug. *** (In reply to Benedikt Ziemons from comment #9) > > Could you please try with the new 121 release, 121.0.6167.139, or with 122.0.6261.6-r1 and let me know if you still hit the issue? > > I am also affected and I just tried 122.0.6261.6-r1 and still hit the issue. Hm. Does USE="-lto" make any difference? It seems to be a common factor based on the logs we have currently. I'm going to kick off a build myself but it's bedtime-ish here. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=95313c187c3dfcf8964cd9a4b1b827fab2ba619b commit 95313c187c3dfcf8964cd9a4b1b827fab2ba619b Author: Matt Jolly <Matt.Jolly@footclan.ninja> AuthorDate: 2024-01-31 22:01:29 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-01-31 22:04:45 +0000 www-client/chromium: fix broken LTO builds Closes: https://bugs.gentoo.org/923032 Signed-off-by: Matt Jolly <Matt.Jolly@footclan.ninja> Closes: https://github.com/gentoo/gentoo/pull/35122 Signed-off-by: Sam James <sam@gentoo.org> www-client/chromium/Manifest | 4 ++-- www-client/chromium/chromium-121.0.6167.139.ebuild | 2 +- www-client/chromium/chromium-122.0.6261.6-r1.ebuild | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) *** Bug 923297 has been marked as a duplicate of this bug. *** |
