Cargo puts the library in target/x86_64-unknown-linux-gnu/release/ instead of target/release/ where Perry expects it

[Lebei2046]

My AI is facing a problem.

[proggeramlug]

Thanks for reporting this — it is a real bug in Perry, not a misuse on your end. Filed and fixed as #564 (commit acaa8ea9 on main).

Root cause: when something pins a default target on your machine — [build] target = "..." in .cargo/config.toml, CARGO_BUILD_TARGET env var, or a rust-toolchain.toml with targets = [...] — cargo writes artifacts to target/<host-triple>/release/ instead of target/release/. Three sites in Perry only probed target/release/ for native builds, so the link/validate/companion-copy step couldn't find the library. The fix probes both layouts (bare target/release/ and target/<host-triple>/release/ derived from rustc -vV's host: line).

Two ways forward:

1. Wait for the next release. The fix is in main and will ship in the next patch (v0.5.645). If you build Perry from source, git pull && cargo build --release -p perry-runtime -p perry-stdlib -p perry picks it up immediately.

2. Unblock yourself today with one of these workarounds in your native-library crate:

   • Remove the [build] target = "..." line from .cargo/config.toml (project, workspace, or ~/.cargo/config.toml), then cargo clean && cargo build --release — artifact lands in target/release/ where the old Perry expected it.
   • Or env -u CARGO_BUILD_TARGET cargo build --release if it's coming from the env.
   • Or quick symlink: ln -s x86_64-unknown-linux-gnu/release target/release inside the native-lib crate.

Hope this unblocks you — please reopen if anything still bites after upgrading.