You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
From what I understand this is just an issue with the website instructions, right?
Correct.
The CI cross-compiles for aarch64-unknown-linux-gnu all the time, so I'm assuming there is no problem with the Cross.toml in the repository.
Only now I realize the name of that file is Cross.toml. My brain read it as Cargo.toml (capital-C + toml, how many could there be?) so the problem was self-inflicted!
However, since the instructions (webside only!) have target also as a command argument, and since my steps worked without changes to Cross.toml, perhaps the section on adding lines to it can be omitted?
This text:
# Create and edit a Cross.toml file in the root of the cloned repo.
vim Cross.toml
Add the following to the Cross.toml. Which will define to cross which container should be used for the target architecture:
[target.armv7-unknown-linux-gnueabihf]
image = "crossimage"
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..
If I remove the changes to
Cargo.toml
,cross build
seems to work and I can see:This leads me to believe that something has changed - perhaps in
cross
itself? - and the instructions should reflect that.To Reproduce
Expected behavior
No response
Stacktrace
Operating System
Linux (Ubuntu)
Additional context
No response
The text was updated successfully, but these errors were encountered: