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
error: couldn't read /Users/runner/work/coreutils/coreutils/target/aarch64-apple-darwin/debug/build/fts-sys-bdca82aeb17ec986/out/fts-sys.rs: No such file or directory (os error 2)
--> /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fts-sys-0.2.14/src/lib.rs:24:1
|
24 | include!(concat!(env!("OUT_DIR"), "/fts-sys.rs"));
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: this error originates in the macro `include` (in Nightly builds, run with -Z macro-backtrace for more info)
error: could not compile `fts-sys` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
Error: Process completed with exit code 101.
It's a bit unfortunate that fts-sys gets pulled. I think it's only required by chcon (selinux), which makes no sense on MacOS. But I'm not sure if there's a way around this.
Similar to #7392, it would be nice to run all tests in CI, on MacOS (basically adding
workspace-tests: true
to bothmacos
jobs in the matrix).When I tried in #7386, I hit this issue:
It's a bit unfortunate that
fts-sys
gets pulled. I think it's only required bychcon
(selinux
), which makes no sense on MacOS. But I'm not sure if there's a way around this.I think the easiest will be to patch
fts-sys
to generate an empty crate on non-supported platforms: https://codeberg.org/koutheir/fts-sys/issues/3There might be more issues after that one gets fixed.
The text was updated successfully, but these errors were encountered: