Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out an 390x build error #381

Closed
sunfishcode opened this issue Jul 11, 2022 · 1 comment
Closed

Figure out an 390x build error #381

sunfishcode opened this issue Jul 11, 2022 · 1 comment

Comments

@sunfishcode
Copy link
Member

In coreos/rpm-ostree#3839, they're seeing this error:

--> /builddir/build/BUILD/rpm-ostree-2022.10.110.gad3fecdc/vendor/rustix/src/imp/libc/fs/dir.rs:47:18
   |
47 | use libc_errno::{errno, set_errno, Errno};
   |                  ^^^^^  ^^^^^^^^^  ^^^^^ no `Errno` in the root
   |                  |      |
   |                  |      no `set_errno` in the root
   |                  no `errno` in the root

This is a surprising error message; it's not the "unresolved import libc_errno" error one might expect if we got the complex cfg wrong in Cargo.toml. Here, the build system seems to have correctly decided that we're using the libc dependencies, and the compiler appears to have found libc_errno. It appears it isn't finding the things inside of it 🤔 .

The errno crate doesn't have any way to disable errno, set_errno, and Errno; those are always unconditionally defined.

So I don't currently have any theories for what might be causing this.

@sunfishcode
Copy link
Member Author

Ah, it's likely that this error is due to cargo-vendor-filterer, which truncates source files to zero length when it thinks they aren't in use. So this is likely just a case of incorrect dependencies, rather than being something mysterious. If anyone sees this error, please report it, but for now, I don't think there's anything immediate that needs to be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant