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
I clone the repo, change to the cli folder, and issue: cargo vendor. I then create the .cargo/config as instructed. However, attempting an offline build with cargo build --offline results in this error:
error: failed to run custom build command for `zstd-sys v1.6.0+zstd.1.5.0`
Caused by:
process didn't exit successfully: `/home/jamin/tmp/askalono/cli/../target/debug/build/zstd-sys-f29cef9d59229dd4/build-script-build` (exit status: 101)
--- stderr
thread 'main' panicked at 'Folder 'zstd/lib' does not exists. Maybe you forgot to clone the 'zstd' submodule?', /home/jamin/tmp/askalono/cli/vendor/zstd-sys/build.rs:180:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed
The cli/vendor/zstd-sys folder is indeed missing the zstd/lib folder.
However, checking the same crate version shows that the folder is present in the crate.
This is an issue with zstd-sys v1.6.0. It had an exclude pattern which prevented the zstd directory from being included. You'll need to update to a newer version of zstd (which appears like you already have).
Problem
I tried to configure https://github.com/jpeddicord/askalono for building offline.
I clone the repo, change to the cli folder, and issue:
cargo vendor
. I then create the.cargo/config
as instructed. However, attempting an offline build withcargo build --offline
results in this error:The
cli/vendor/zstd-sys
folder is indeed missing thezstd/lib
folder.However, checking the same crate version shows that the folder is present in the crate.
Steps
git clone https://github.com/jpeddicord/askalono
askalono/cli
cargo vendor
../.cargo/config
cargo build --offline
Possible Solution(s)
No response
Notes
No response
Version
The text was updated successfully, but these errors were encountered: