Our rust could be too old to keep updating chromium-browser See bug#34394 comment#4
Rust 1.80.0 should be enough according to upstream PR: https://github.com/rust-lang/rust/pull/124678#event-12703606396. Upstream commit: https://github.com/rust-lang/rust/commit/93ca906cb572d8754dc43773a3cd502717fd8f07
Summary: Update Request: rust version 1.85.0 => Update Request: rust version 1.80.0
(In reply to Jani Välimaa from comment #1) > Rust 1.80.0 should be enough according to upstream PR: > https://github.com/rust-lang/rust/pull/124678#event-12703606396. > > Upstream commit: > https://github.com/rust-lang/rust/commit/ > 93ca906cb572d8754dc43773a3cd502717fd8f07 Did you take this or is it fine if I do?
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=34480
Assignee: pkg-bugs => j.alberto.vc
Depends on: (none) => 34507
With rust 1.80.0 firefox i586 still fail with rustc-LLVM ERROR: Cannot emit physreg copy instruction Even with the patch I find for llvm19, so could be necessary to update llvm19-suite, but is not clear to what version
CC: (none) => jani.valimaa
(In reply to katnatek from comment #3) > With rust 1.80.0 firefox i586 still fail with > > rustc-LLVM ERROR: Cannot emit physreg copy instruction > > Even with the patch I find for llvm19, so could be necessary to update > llvm19-suite, but is not clear to what version For this special package I recommend to request an exception to updates policy and update to the latest one, 19.1.7.
(In reply to Jani Välimaa from comment #1) > Rust 1.80.0 should be enough according to upstream PR: > https://github.com/rust-lang/rust/pull/124678#event-12703606396. > > Upstream commit: > https://github.com/rust-lang/rust/commit/ > 93ca906cb572d8754dc43773a3cd502717fd8f07 It seems that even if Rust 1.80 is enough, it should be updated to 1.81 just to fix https://bugs.mageia.org/show_bug.cgi?id=33522 while you're updating Rust anyway.
CC: (none) => zooplah
Due bug#34394 comment#9 I not have a valid motive to request the update Tested building firefox in all architectures, just with a change for i586
Depends on: 34507 => (none)Blocks: 34394 => (none)
CC: (none) => marja11Summary: Update Request: rust version 1.80.0 => Update Request: rust version 1.82, needed to build FF and TB 140.3.1 with security fixes.Blocks: (none) => 34637, 34638
High priority because it blocks security updates of applications.
CC: (none) => friPriority: Normal => High
rust 1.80.1 looks good to build current firefox, working on 1.81.0 now
Tested 1.81.0 But I'm experimenting issues building 1.82.0, currently testing if use llvm19-suite make some difference
Created attachment 15135 [details] Build Fail in 64bit aarch64 and i586 keep building but x86_64 fails Maybe llvm 19 suite need update :S
This is beyond my skills Rust 1.82.0 fails With llvm17-suite all architectures fail https://copr.fedorainfracloud.org/coprs/katnatek/mgaMentorship/build/9678529/ With current llvm19-suite x86_64 fail https://copr.fedorainfracloud.org/coprs/katnatek/mgaMentorship/build/9680140/ With llvm19-suite 19.1.7 x86_64 fail in other point https://copr.fedorainfracloud.org/coprs/katnatek/mgaMentorship/build/9681652/ Did you need I upload the changes to rust to make deep analysis?
Assignee: j.alberto.vc => pkg-bugs
@katnatek. We build Firefox every month on the Mageia Linux Online community repository. We bundle rust with Firefox and does not follow Mageia packaging rules. However, maybe you can use our package as an inspiration. You can find the source package here : https://repository.mageialinux-online.org/9/SRPMS/media/core/firefox-release-143.0.4-1.yuu.mlo9.src.rpm
CC: (none) => cyril.levet0780
(In reply to Cyril Levet from comment #12) > @katnatek. We build Firefox every month on the Mageia Linux Online community > repository. We bundle rust with Firefox and does not follow Mageia packaging > rules. However, maybe you can use our package as an inspiration. You can > find the source package here : > https://repository.mageialinux-online.org/9/SRPMS/media/core/firefox-release- > 143.0.4-1.yuu.mlo9.src.rpm Not my decision, will be just for 64b as rust 1.82.0 builds at less in aarch64,i586, but I'm not the firefox packager
Why not go beyond llvm19-suite? Maybe 20 or 21 would do?
CC: (none) => imek5
(In reply to i mek from comment #14) > Why not go beyond llvm19-suite? Maybe 20 or 21 would do? I'm building 20.1.0 right now to test
llvm 20.1.0 not helps and I think goes beyond 19 will not help https://copr.fedorainfracloud.org/coprs/katnatek/mgaMentorship/build/9688199/ I'll will try add mageia patches to llvm 19.1.7 and/or build rust 1.83.0
Not luck with llvm19-suite 19.1.7 + some mageia patches, just delay a few more to x86_64 to fail Compiling glob v0.3.1 rustc: /builddir/build/BUILD/llvm-project-llvmorg-19.1.7/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:303: void llvm::Loc::MMI::addFrameIndexExpr(const llvm::DIExpression *, int): Assertion `(FrameIndexExprs.size() == 1 || llvm::all_of(FrameIndexExprs, [](const FrameIndexExpr &FIE) { return FIE.Expr && FIE.Expr->isFragment(); })) && "conflicting locations for variable"' failed. rustc exited with signal: 6 (SIGABRT) (core dumped) error: could not compile `cargo` (lib) I think I must send 1.82.0 as is and Nicolas should bundle rust 64b for the 64bit build But is not my decision, I will try with 19.1.3 that is more close to llvm version bundled in rust 1.82.0
CC: (none) => nicolas.salguero
I find a rust upstream report https://github.com/rust-lang/rust/issues/131944 And a PR https://github.com/rust-lang/rust/pull/132613 I will try with that
Well as the issue is related with defective debuginfo I decide to reduce debuginfo on all architectures, for the moment looks good it passes all the previous fail points, perhaps is not the best solution but all others fail. I'll keep informing or send the change to BS if ends good
The build ends but I want to try one more PR https://github.com/rust-lang/rust/pull/138818 to see if builds with the normal debuginfo in x86_64
RPMS: cargo-1.82.0-1.mga9 clippy-1.82.0-1.mga9 rust-1.82.0-1.mga9 rust-analyzer-1.82.0-1.mga9 rust-debugger-common-1.82.0-1.mga9 rust-doc-1.82.0-1.mga9 rust-gdb-1.82.0-1.mga9 rust-lldb-1.82.0-1.mga9 rust-src-1.82.0-1.mga9 rust-std-static-1.82.0-1.mga9 rust-std-static-i686-pc-windows-gnu-1.82.0-1.mga9 rust-std-static-wasm32-unknown-unknown-1.82.0-1.mga9 rust-std-static-wasm32-wasi-1.82.0-1.mga9 rust-std-static-wasm32-wasip1-1.82.0-1.mga9 rust-std-static-x86_64-pc-windows-gnu-1.82.0-1.mga9 rust-std-static-x86_64-unknown-none-1.82.0-1.mga9 rust-std-static-x86_64-unknown-uefi-1.82.0-1.mga9 rustfmt-1.82.0-1.mga9
Assignee: pkg-bugs => qa-bugs
In response to comment 21. I hope it works well katnatek, great job! Firefox and Thunderbird updates are closer.
CC: (none) => Joselp
(In reply to Jose Manuel López from comment #22) > In response to comment 21. I hope it works well katnatek, great job! > > Firefox and Thunderbird updates are closer. https://www.openwall.com/lists/oss-security/2025/09/24/11 "just a quick note that libexpat 2.7.3 (or "Expat 2.7.3") released today is improving upon the original fixes to CVE-2024-8176 and CVE-2025-59375. So if you backported the original fixes, please be sure to update/extend these backports as needed."
Used to build firefox 140.4.0 without issues in 3 architectures, arm fail is as I understand due limitations of the architecture. Used to build rust-cbindgen in all architectures without issue I'll upload advisory tomorrow
Whiteboard: (none) => MGA-9-64-OK,MGA-9-32-OK
Cool. I've been concerned about this one. I'm not at all qualified to do any tests on it other than maybe a clean install, so I couldn't help. Thanks for your hard work! Validating.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => advisory
Whiteboard: MGA-9-64-OK,MGA-9-32-OK => MGA9-64-OK,MGA9-32-OK
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2025-0086.html
Status: NEW => RESOLVEDResolution: (none) => FIXED