rust-embedded / rust-embedded/linux-embedded-hal

Get "-bash: ./test: No such file or directory" error on BeagleBone

Open
#54 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
319
Forks
60
Avg merge
12h 31m
Merged PRs (30d)
1

Description

When I use the below configuration and cross compile to ARMv7 I get the following error message on the BeagleBone:

debian@beaglebone:~$ ./test 
-bash: ./test: No such file or directory

When I use v0.2.2 of linux-embedded-hal or earlier I do not get this error. If I remove extern crate linux_embedded_hal as hal; from the code I do not get the error.

Any ideas?

The code

src/main.rs

extern crate linux_embedded_hal as hal;

fn main() {
    println!("Hello");
}

.cargo/config

[target.armv7-unknown-linux-musleabihf]
linker = "arm-linux-gnueabihf-gcc"
rustflags = ["-Clink-args=-Xlinker -rpath=/usr/lib/arm-linux-gnueabihf"]

Cargo.toml

[package]
name = "test"
version = "0.1.0"
edition = "2018"

[dependencies]
linux-embedded-hal = "0.4.0-alpha.0"

To compile I use:

cargo build --target=armv7-unknown-linux-musleabihf --release

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the ARMv7 release build with src/main.rs, Cargo.toml, and .cargo/config, then compare the result with linux-embedded-hal 0.2.2 and without the dependency. Inspect the generated executable and its runtime requirements on the BeagleBone; done means the compiled test starts successfully with the dependency present.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, rust
Domain
build-system, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.