TechOverflow Logo
TechOverflow

Cargo : comment corriger le crash error: failed to run custom build command for `hdf5-sys v0.8.1`

English Français

Problème

Pendant cargo build ou cargo run, vous voyez un message d’erreur tel que

cargo-hdf5-sys-error.txt
error: failed to run custom build command for `hdf5-sys v0.8.1`

Caused by:
  process didn't exit successfully: `/home/uli/dev/Versatile/RustyMatrix/target/debug/build/hdf5-sys-555129b7288a757c/build-script-build` (exit status: 101)
  --- stdout
  Attempting to find HDF5 via pkg-config...
  cargo:rerun-if-env-changed=HDF5_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=HDF5_STATIC
  cargo:rerun-if-env-changed=HDF5_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr

  thread 'main' (963963) panicked at /home/uli/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/hdf5-sys-0.8.1/build.rs:548:13:
  Unable to locate HDF5 root directory and/or headers.
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

Solution

Votre projet Rust dépend de la crate hdf5-sys, qui à son tour dépend de la bibliothèque système hdf5.

Bien que vous puissiez l’installer avec sudo apt -y install libhdf5-dev, selon votre version d’Ubuntu cela pourrait installer une version non prise en charge par la crate hdf5-sys.

Par conséquent, je recommande de modifier votre Cargo.toml pour activer spécifiquement la fonctionnalité static, qui compile directement une version compatible de libhdf5.

Cargo.toml
hdf5 = "0.8.1"
hdf5-sys = { version = "0.8.1", features = ["static"] }

Ensuite, vous pouvez relancer votre commande cargo.

Check out similar posts by category: Rust