Closed tarcieri closed 4 years ago
error[E0463]: can't find crate for `core`
|
= note: the `armv7a-none-eabi` target may not be installed
It should be noted in the docs that you need rustup target add armv7a-none-eabi
[bascule@strangelove firmware]$ cargo build --example blinky
(..)
= note: rust-lld: error: undefined symbol: __stack_top__
The command needs to be run from the usbarmory
directory (this is noted in the docs). That's the only directory that contains the Cargo configuration file (.cargo/config
) to pass the -Tlink.x
to the linker. The error you are seeing comes from not passing that linker script to the linker. I guess we could also move that Cargo configuration file to the the root of the workspace then builds from firmware
should also work.
[1] 4783 killed cargo build --example blinky
Intriguing. Can you re-run this as cargo build --example blinky -j1 -v
to see which crate is generating the OOM. It could be that a build script has unintentional infinite recursion on mac.
Thanks! All working now and I was able to load an ELF image.
I think the OOM om Mac might've been a bug in that nightly release. I experienced something similar compiling an unrelated project.
I've updated to the latest nightly rustc 1.42.0-nightly (3761dcd34 2020-01-28)
and am no longer experiencing the problem.
A couple different problems on a couple different OSes. Both are using
rustc 1.42.0-nightly (8a79d08fa 2020-01-27)
and trying to build commit d6814dca.CentOS Linux release 8.1.1911 (Core):
This is macOS Catalina (16GB RAM host, potentially OOM?)