test-cargo-miri: add proc-macro2 instead of anyhow

Author: RalfJung

src/tools/miri/test-cargo-miri/Cargo.lock

@@ -2,12 +2,6 @@
 # It is not intended for manual editing.
 version = 3
 
-[[package]]
-name = "anyhow"
-version = "1.0.81"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "0952808a6c2afd1aa8947271f3a60f1a6763c7b912d210184c5149b5cf147247"
-
 [[package]]
 name = "autocfg"
 version = "1.1.0"
@@ -30,7 +24,6 @@ checksum = "14c189c53d098945499cdfa7ecc63567cf3886b3332b312a5b4585d8d3a6a610"
 name = "cargo-miri-test"
 version = "0.1.0"
 dependencies = [
- "anyhow",
  "autocfg",
  "byteorder 0.5.3",
  "byteorder 1.4.3",
@@ -42,6 +35,7 @@ dependencies = [
  "issue_1705",
  "issue_1760",
  "issue_rust_86261",
+ "proc-macro2",
  "serde_derive",
 ]
 

src/tools/miri/test-cargo-miri/Cargo.toml

@@ -20,12 +20,13 @@ issue_rust_86261 = { path = "issue-rust-86261" }
 
 [dev-dependencies]
 byteorder_2 = { package = "byteorder", version = "0.5" } # to test dev-dependencies behave as expected, with renaming
-# Not actually used, but exercises some unique code path (`--extern` .so file).
+## More dependencies that we don't actually use, but add just for extra test coverage.
+# Exercises some unique code path (`--extern` .so file).
 serde_derive = "1.0.185"
-# Not actually used, but uses a custom build probe so let's make sure that works.
+# These use custom build probes, let's make sure they don't explode.
 # (Ideally we'd check if the probe was successful, but that's not easily possible.)
-anyhow = "1.0"
-# Same as anyhow.
+# proc-macro2 is extra exciting because it is both a host-dependency and a target-dependency.
+proc-macro2 = "1.0"
 eyre = "0.6"
 
 [build-dependencies]