Repository navigation
Missing SO_INCOMING_CPU compiling with armv7-unknown-linux-musleabi #213
Description
Activity
- added a commit that references this issue
on Mar 17, 2021 Changed in libc is already merged. Consider fixed the lowest libc version in the next release.
Thanks for finding and solving the problem @zonyitoo.
Reacted by tySorry to borrow this issue, but I found out
aarch64-unknown-linux-muslandx86_64-unknown-linux-musltargets are also broken the same way and made a pull request tolibccrate to getSO_INCOMING_CPUimplemented there.Reacted by Thomas de Zeeuw, ty and Tim ViséeUntil the next version of libc is released, is there a known workaround, such as pinning a specific version of libc or socket2?
@fbecart can you run
cargo update, updating the libc crate? That should resolve this issue.Reacted by Ossi HerralaThank you @Thomasdezeeuw for pointing me in the right direction. I realize the problem is currently fixed for a specific set of architectures only. I'm building for
i686-unknown-linux-musl, for which an issue likely still exists. I'll redirect my attention tolibc.There are still many architectures missing
SO_INCOMING_CPUin thelibccrate. Could @Thomasdezeeuw make sure that all Linux-like platforms have this definition inlibc?I am not sure that
target-env = "uclibc"hasSO_INCOMING_CPUdefinition. It is left for others to make patches. :)I think this issue is really with libc, not with socket2.
I meet this issue too.
error[E0425]: cannot find value `SO_INCOMING_CPU` in crate `libc` --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.4.0/src/sys/unix.rs:1201:69 | 1201 | getsockopt::<c_int>(self.inner, libc::SOL_SOCKET, libc::SO_INCOMING_CPU) | ^^^^^^^^^^^^^^^ not found in `libc` error[E0425]: cannot find value `SO_INCOMING_CPU` in crate `libc` --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.4.0/src/sys/unix.rs:1217:23 | 1217 | libc::SO_INCOMING_CPU, | ^^^^^^^^^^^^^^^ not found in `libc` error: aborting due to 2 previous errors For more information about this error, try `rustc --explain E0425`. error: could not compile `socket2` To learn more, run the command again with --verbose.how to work around?
@JinAirsOs you can disable the
allfeature for now to work around it. Otherwise I think rust-lang/libc#2135 would fix this issue.- added 8 commits that reference this issue
on Apr 2, 2021
This was originally found in shadowsocks/shadowsocks-rust#459 .