Linking with rust issue. #277
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi, I have an issue that started recently whenever I try to build rust code against libs from this repository. I can build just fine against official Arch repos. Example from AUR:
cinny-desktop
.Result in:
Flags are
-Ctarget-cpu=native -Clink-dead-code=off -Copt-level=2
. I also tried to disable LTO withoptions=(!lto)
. I tested against -v3 and -v4 repos.Doing
objdump -x /usr/lib/rustlib/x86_64-unknown-linux-gnu/lib/libproc_macro-68e7be1c71cd87ea.rlib
result in the samefile format not recognized
error. Could it has gotten corrupted?I tested the package from different mirrors and same issue.
I also ran into the issue when trying to recompile mesa locally.
Can you try to rebuild rust locally with the relevant makepkg.conf from here: https://alhp.dev/makepkg/
and check if the issue also happens with that package?
This is to rule out a maybe temprorary build-time problem. If the issue is reproducible, that would mean that rust is not compatible with the optimizations anymore and should maybe be blacklisted.
Unfortunately I don't have time myself to help with the debugging in the next days.
ok found some time to compile rust locally.
@anonfunc can you add rust to the non-LTO packages and trigger a rebuild? Or are there other things that should be checked first?
Thanks for figuring this out, rebuild is on the way.
no worries. Something seems to have gone wrong though -
rust 1:1.89.0-1.2
still produces the error, and the status page shows that it is still an LTO build.I think the status page thing does not update correctly. I'll check later.
I have been unable to compile
proton-cachyos
for a while now. System is updated with the latest rust. Just got thislibproc_macro
error too.output from yay
extra-x86-64-v3/rust 1:1.89.0-1.2 (66.3 MiB 255.8 MiB) (Installed)
@anonfunc i tried again with rebuilding rust with the non-lto.conf and it still produces a usable rust package. The version in the repository is still producing the error.
Yep my fault, I think I missed the config reload after adding it to the LTO exceptions. Rebuild is queued.
@anonfunc I think you need to rebuild
lib32-rust-libs
too. I just can't find it in https://status.alhp.dev/?pkgbase=lib32-rust-libsThe
lib32-rust-libs
package is a split package of rust: https://archlinux.org/packages/extra/x86_64/rust/ and will be rebuild when the base package is anyways.rust 1:1.89.0-1.3
looks good, can't trigger the error any more. Thanks!Sorry, email notifications got caught by spam filters. The new version works fine, thank you very much.