You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rust-lld is unaware of system libraries and seems like there is no way
to point it to them. That often triggers issues like:
```
cargo:warning=error: linking with `rust-lld` failed: exit status: 1ger, ppv-lite86, libc...
cargo:warning= |
cargo:warning= = note: LC_ALL="C" PATH="/home/vadorovsky/.rustup/toolchains/stable-x86_64-un
cargo:warning= = note: rust-lld: error: unable to find library -lgcc_s
cargo:warning= rust-lld: error: unable to find library -lc
cargo:warning=
cargo:warning=
cargo:warning=
cargo:warning=error: aborting due to 1 previous error
```
Using system-wide LLD makes the issue disappear.
Fixesaya-rs#907
Happens every time on Gentoo with musl-llvm profile, but it's likely to happen on non-GNU userlands in general:
Specifying
-L /lib -L /usr/lib
doesn't help, even though I have llvm-libgcc and musl in these directories (both shared and static).It originally happened in CI in my cross build / binstall attempts here: https://github.com/aya-rs/bpf-linker/actions/runs/8267383737/job/22617773928?pr=129
Using system-wide LLD makes the issue disappear.
The text was updated successfully, but these errors were encountered: