Open
Description
Describe the bug
Wanting to have probe-rs
run on Raspberry Pi 3B hardware, I'm following Crosscompiling instructions.
In my case I'm running these within a Multipass VM (Ubuntu), but let's pretend that's not the cause..
$ cross build -p probe-rs-tools --release --target=armv7-unknown-linux-gnueabihf
[cross] warning: unable to get metadata for package
[cross] note: Falling back to `cargo` on the host.
error: failed to parse manifest at `/home/ubuntu/probe-rs/Cargo.toml`
Caused by:
this virtual manifest specifies a `target` section, which is not allowed
If I remove the changes to Cargo.toml
, cross build
seems to work and I can see:
$ file target/armv7-unknown-linux-gnueabihf/release/probe-rs
target/armv7-unknown-linux-gnueabihf/release/probe-rs: ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0, BuildID[sha1]=3214d84cfb4b080e1e0dd6530341621c70320eb3, not stripped
This leads me to believe that something has changed - perhaps in cross
itself? - and the instructions should reflect that.
To Reproduce
- Follow the instructions, on Ubuntu
- Does the final command succeed?
Expected behavior
No response
Stacktrace
Operating System
Linux (Ubuntu)
Additional context
No response
Metadata
Metadata
Assignees
Labels
No labels