inconsistency between verus version in Cargo.toml and Cargo.lock

[astefano]

Hello,

From Cargo.toml, i thought we need verus version 0.2025.11.30.840fa61 but i get:

...verified-storage/capybaraKV/capybarakv [main|…1]  $ cargo-verus verify
...
error: failed to run custom build command for `capybarakv v0.1.0 (/home/lacra/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv)`

Caused by:
  process didn't exit successfully: `/home/lacra/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv/target/debug/build/capybarakv-537251953bb82403/build-script-build` (exit status: 101)
  --- stdout
  cargo:rustc-link-lib=pmem

  --- stderr
  wrapper.h:1:10: fatal error: 'libpmem.h' file not found

  thread 'main' (3979470) panicked at build.rs:15:10:
  Unable to generate bindings: ClangDiagnostic("wrapper.h:1:10: fatal error: 'libpmem.h' file not found\n")
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

thread 'rustc' (3979467) panicked at rust_verify/src/verus_items.rs:621:17:
unexpected verus diagnostic item verus::verus_builtin::real
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: could not compile `vstd` (lib)

Caused by:
  process didn't exit successfully: `/home/lacra/verus/verus /home/lacra/.rustup/toolchains/nightly-2025-09-01-x86_64-unknown-linux-gnu/bin/rustc --crate-name vstd --edition=2021 /home/lacra/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/vstd-0.0.0-2026-01-11-0057/vstd.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=184 --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --warn=unexpected_cfgs --check-cfg 'cfg(verus_keep_ghost)' --check-cfg 'cfg(verus_verify_core)' --check-cfg 'cfg(verus_keep_ghost_body)' --cfg 'feature="alloc"' --cfg 'feature="default"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("alloc", "allocator", "allow_panic", "default", "std", "strict_provenance_atomic_ptr"))' -C metadata=6762e5498c6ebddf -C extra-filename=-9a5ada7852cada41 --out-dir /home/lacra/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv/target/debug/deps -L dependency=/home/lacra/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv/target/debug/deps --extern verus_builtin=/home/lacra/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv/target/debug/deps/libverus_builtin-c3f8860ce9284869.rmeta --extern verus_builtin_macros=/home/lacra/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv/target/debug/deps/libverus_builtin_macros-dad708294cfa23c9.so --extern verus_state_machines_macros=/home/lacra/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv/target/debug/deps/libverus_state_machines_macros-81b2523d07c9541f.so --cap-lints allow` (exit status: 1)

Cargo.lock suggests we need a more recent verus, so i tried with: 0.2026.01.10.531beb1 which is the closest to "0.0.0-2026-01-11-0057" which we see in Cargo.lock. With this version, i get:

$ cargo-verus verify
   Compiling vstd v0.0.0-2026-01-11-0057
   Compiling capybarakv v0.1.0 (/home/lacra/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv)
error: failed to run custom build command for `capybarakv v0.1.0 (/home/lacra/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv)`

Caused by:
  process didn't exit successfully: `/home/lacra/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv/target/debug/build/capybarakv-7e18f8097b82facf/build-script-build` (exit status: 101)
  --- stdout
  cargo:rustc-link-lib=pmem

  --- stderr
  wrapper.h:1:10: fatal error: 'libpmem.h' file not found

  thread 'main' (3983372) panicked at build.rs:15:10:
  Unable to generate bindings: ClangDiagnostic("wrapper.h:1:10: fatal error: 'libpmem.h' file not found\n")
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
verification results:: 1341 verified, 0 errors

Not sure if the error is known.
In any case, i was wondering if Cargo.toml should be updated.

Thank you,
Lacramioara

[jaylorch]

Thanks for letting us know! Sorry it took a couple of weeks to notice your issue.

The problem may be that you don't have PM dependencies installed. In that case, you should use the --no-default-features command-line argument, i.e., run cargo verus verify --no-default-features instead of cargo verus verify.

[jaylorch]

As for the mismatch between the Verus version and the latest Verus, I've made a pending PR for that. #42

[hayley-leblanc]

Hi @astefano, could you see if the most recent commit fixes your error? Like Jay said, it looks like you should also include --no-default-features to skip the PM dependencies.

[astefano]

Thank you both, i confirm that with verus 0.2026.01.23.1650a05, cargo-verus verify --no-default-features works fine:

~/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv [main|…1] 
18:48 $ cargo-verus verify --no-default-features
   Compiling verus_prettyplease v0.0.0-2026-01-25-0057
   Compiling verus_state_machines_macros v0.0.0-2026-01-25-0057
   Compiling capybarakv v0.1.0 (/home/lacra/git_repos/baif/verus_projects/verified-storage/capybaraKV/capybarakv)
   Compiling verus_builtin_macros v0.0.0-2026-01-25-0057
   Compiling vstd v0.0.0-2026-01-25-0057
verification results:: 1341 verified, 0 errors
verification results:: 722 verified, 0 errors
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 34.11s