Closed ManOrs88 closed 2 years ago
The reflink master (already 2 years old) has a fix for that, try using that one instead of the one from crates.io by changing the reflink = "0.1.3"
line in Cargo.toml
to
reflink = { git = "https://github.com/nicokoch/reflink.git", rev = "e8d93b465f5d9ad340cd052b64bbc77b8ee107e2" }
Also happens with cargo build in Debian armhf/arm7vl (Raspberry Pi). Dunno if this is relevant but just putting it here for search engines.
Using the reflink (check out the repo, change Cargo.toml
as above, do a cargo build --release
) works.
The reflink master (already 2 years old) has a fix for that, try using that one instead of the one from crates.io by changing the
reflink = "0.1.3"
line inCargo.toml
to
Is there any reason fclones isn't using that version?
It is not possible to publish a crate that relies on an unpublished crate. All dependencies must be in crates.io.
RE: Piotr
Oh I see, that's just perfect 😆
Through the magic of #[cfg(..)]
reflink should not bother you any longer!
Unless you want to test fclones... I only left reflink active in the Linux build to test the macOS/Windows code paths, but these need not be build for the fclones binary itself.
hello, I'm unable to (cross)compile a musl binary on aarch64 ("cross" as in from ubuntu, still aarch64) [also tried compiling native on alpine aarch64, same result]
compiling with glibc works correctly
(rust 1.57.0)
regards, m