- Status Closed
- Percent Complete
- Task Type Bug Report
- Category Packages
-
Assigned To
Andreas Baumann - Operating System pentium4
- Severity Low
- Priority Medium
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Attached to Project: Arch Linux 32
Opened by Andreas Baumann - 27.01.2021
Last edited by Andreas Baumann - 18.02.2021
Opened by Andreas Baumann - 27.01.2021
Last edited by Andreas Baumann - 18.02.2021
FS#138 - polkit doesn't build because of a stuck js78
Closed by Andreas Baumann
18.02.2021 14:14
Reason for closing: Fixed
Additional comments about closing:
18.02.2021 14:14
Reason for closing: Fixed
Additional comments about closing:
js78 builds with rust148
Some rust things fail:
So this boils down to fixing Rust for 1.49 first and hope it will build with that version
(or alternatively we could also try rust148 first).
using clang target –target=i686-unknown-linux-gnu
Interesting:
ls /usr/lib/clang/
reveils a 11.0.0 and a 11.0.1
the include files are in 11.0.0, the libraries in 11.0.1 and the builds
search for the libraries in 11.0.0:
ld.lld: error: cannot open /usr/lib/clang/11.0.0/lib/linux/libclang_rt.profile-i386.a: No such file or directory
This sounds like a misbuild of clang..
Let's blindly reschedule clang and llvm builds.
Now check fails in some Python test code. To me it's not clear whether this
is a general Python issue or just this test framework.
We have a rust version which cannot compile older versions of js now?
Let's try to pin rust to 1.49 or rust 148 (on pentium4 as we have rust 1.50 there already).
So js78 compiles on i686 because rust 1.50 failed to build.
This is software development in 2021 at its best!