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: failed to run custom build command for `libsodium-sys v0.2.6 (/usr/ports/net/cjdns/work/sodiumoxide-9f6a18d40a4db253edfebac9f2ce5c22d09b1f47/libsodium-sys)`
Caused by:
process didn't exit successfully: `/usr/ports/net/cjdns/work/cjdns-cjdns-v22/target/release/build/libsodium-sys-e46d303e5445fd4d/build-script-build` (exit status: 101)
--- stdout
cargo:rerun-if-env-changed=SODIUM_LIB_DIR
cargo:rerun-if-env-changed=SODIUM_SHARED
cargo:rerun-if-env-changed=SODIUM_USE_PKG_CONFIG
cargo:rerun-if-env-changed=SODIUM_DISABLE_PIE
OPT_LEVEL = Some("2")
TARGET = Some("x86_64-unknown-freebsd")
HOST = Some("x86_64-unknown-freebsd")
CC_x86_64-unknown-freebsd = None
CC_x86_64_unknown_freebsd = None
HOST_CC = None
CC = None
CFLAGS_x86_64-unknown-freebsd = None
CFLAGS_x86_64_unknown_freebsd = None
HOST_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("false")
CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
--- stderr
thread 'main' panicked at /usr/ports/net/cjdns/work/sodiumoxide-9f6a18d40a4db253edfebac9f2ce5c22d09b1f47/libsodium-sys/build.rs:236:89:
Failed to find configure script! Did you clone the submodule at `libsodium-sys/libsodium`?: Os { code: 2, kind: NotFound, message: "No such file or directory" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
Version: 22
FreeBSD 14.0
The text was updated successfully, but these errors were encountered:
yurivict
changed the title
Build fails suggesting to clone the git submodule libsodium-sys/libsodium, but the cjdns repositor has no submodules
Build fails suggesting to clone the git submodule libsodium-sys/libsodium, but the cjdns repository has no submodules
Jun 6, 2024
Failure message:
Version: 22
FreeBSD 14.0
The text was updated successfully, but these errors were encountered: