esp-backtrace (0.12.1) - error[E0583]: file not found for module arc

[Token-Thinker]

I strongly believe it is user error but I can't find the answer. Some assistance would be appreciated.

toolchain = esp

rustc 1.77.0-nightly (424037dcb 2024-03-18) (1.77.0.0)
binary: rustc
host: x86_64-unknown-linux-gnu
release: 1.77.0-nightly
LLVM version: 17.0.1

error[E0583]: file not found for module `arch`
  --> ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-backtrace-0.12.1/src/lib.rs:50:1
   |
50 | pub mod arch;
   | ^^^^^^^^^^^^^
   |
   = help: to create the module `arch`, create file "~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-backtrace-0.12.1/src/arch.rs" or "~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-backtrace-0.12.1/src/arch/mod.rs"
   = note: if there is a `mod arch` elsewhere in the crate already, import it with `use crate::...` instead

error[E0425]: cannot find function `backtrace` in module `crate::arch`
   --> ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-backtrace-0.12.1/src/lib.rs:105:34
    |
105 |     let backtrace = crate::arch::backtrace();
    |                                  ^^^^^^^^^ not found in `crate::arch`

error[E0425]: cannot find value `RA_OFFSET` in module `crate::arch`
   --> ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-backtrace-0.12.1/src/lib.rs:116:52
    |
116 |             println!("0x{:x}", addr - crate::arch::RA_OFFSET);
    |                                                    ^^^^^^^^^ not found in `crate::arch`

Some errors have detailed explanations: E0425, E0583.
For more information about an error, try `rustc --explain E0425`.
error: could not compile `esp-backtrace` (lib) due to 3 previous errors

[MabezDev]

I think you've missed setting the target, and are maybe building for your host machine. Did you use the template to generate your project?

[Token-Thinker]

No, that isn't the issue. My manifest and .cargo config seem to be correct.
This is the first time i'm experiencing this issue on Ubuntu. On other os (Mac) it seems to build just fine and also looking at the files directly in ide (RustRover) it is recognizing that the imports are there which is why i'm a bit baffled.

##########################################################
#                     Build Options                      #
##########################################################
[build]

target = "xtensa-esp32-none-elf"


##########################################################
#                   "General" Settings                   #
##########################################################
[unstable]

build-std = ["alloc", "core"]


##########################################################
#                     ESP32 Options                      #
##########################################################
[target.'cfg(target_arch = "xtensa")']

runner    = "espflash flash --monitor"
rustflags = [
  # GNU LD
  "-C", "link-arg=-Wl,-Tlinkall.x",
  "-C", "link-arg=-nostartfiles",
  "-C", "link-arg=-Trom_functions.x",
]


[target.'cfg(target_arch = "riscv32")']

runner    = "espflash flash --monitor"
rustflags = [
  "-C", "link-arg=-Tlinkall.x",
  "-C", "force-frame-pointers",
  "-C", "link-arg=-Trom_functions.x",
]

[dependencies]

anyhow = { workspace = true }

seq-macro = "0.3.5"

esp-alloc = "0.4.0"
esp-wifi = { version = "0.6.0", features = [
    "esp32",
    "wifi",
    "tcp",
    "udp",
    "embedded-svc",
    "embassy-net"
] }
hal = { package = "esp-hal", version = "0.18.0", features = [
    "esp32",
    "defmt",
    "debug",
    "async",
] }
esp-hal-embassy = { version = "0.1.0", features = [
    "time-timg0",
] }
esp-backtrace = { version = "0.12.0", features = [
    "esp32",
    "panic-handler",
    "exception-handler",
    "defmt",
] }

[MabezDev]

Is your project open source, it might be easier to take a look directly?

[Token-Thinker]

it isn't fully opensource yet. but i just added you to the repo. it is on the refactor-worspace branch under hardware/boards/esp32

[Token-Thinker]

@MabezDev thoughts - still stuck.

[Token-Thinker]

i think i figured it out, you need to set the [target.xtensa-esp32-none-elf.dependencies] in the manifest

[Token-Thinker]

Nope @MabezDev that did not fix the issue and it is really annoying.

i even tried reducing it to example code to isolate the issue however I have no idea for the life of me why this is happening. Please help.

example

#![no_std]
#![no_main]

use hal::{clock::ClockControl, peripherals::Peripherals, prelude::*, system::SystemControl};
use esp_backtrace as _;

#[entry]
fn main() -> ! {
    let peripherals = Peripherals::take();
    let system = SystemControl::new(peripherals.SYSTEM.split());
    let _clocks = ClockControl::max(system.clock_control).freeze();


    panic!("Hello!");
}

manifest

[dependencies]
esp-backtrace = { version = "0.12.0", features = [
    "esp32",
    "exception-handler",
    "panic-handler",
    "defmt"
] }

hal = { package = "esp-hal", version = "0.18.0", features = [
    "esp32",
    "defmt",
] }

dir-structure

.
├── Cargo.lock
├── Cargo.toml
├── hardware
│   ├── boards
│   │   ├── esp32
│   │   │   ├── Cargo.toml
│   │   │   └── src
│   │   │       └── lib.rs
│   ├── build.rs
│   ├── Cargo.toml
│   └── src
│       ├── lib.rs
├── LICENSE-APACHE
├── rustfmt.toml
├── rust-toolchain.toml
├── server
│   ├── Cargo.toml
│   └── src
│       ├── lib.rs
└── test

[asalvo]

I got the same error, and the problem was due to my directory structure. Like you, I was looking to move my source down 1 or more levels in the folder hierarchy. If I run cargo build from the project/repo root I get the error you have posted. If I cd into the root of the directory for my esp32 project (which contains my cargo.toml, build.rs, etc) and run cargo build then my esp32 application compiles correctly.

[Token-Thinker]

Thanks for the reply, I honestly forgot to answer to this. Because I plan on having multiple board types, I opted using xtask to build the project similar to the esp-hal team SHOUT OUT TO THE SMARTIES.

This allowed me to pass the parameters needed to terminal using the cfg tag and build the project based on the board type. In turn this got rid of that error since I'm building packages within packages.

I may need to consider restructuring in the future, but for now it is working-ish hahah