-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo build --release: cannot find macro asm
in this scope
#2
Comments
Hi @jasonm , thanks for taking a look. What is the output of |
Fixes: daily-co#2 For reference: Namespace the asm! macro: rust-lang/rust#84019 Stablization of the asm! macro: https://github.com/rust-lang/reference/blob/cf3a28145e06a3294/src/inline-assembly.md https://phip1611.de/blog/include-assembler-source-files-in-rust-project-and-build-with-cargo
Hi @vipyne thanks for your message! I ended up opening #3 and included my notes below. Versions of
|
Fixed with #3 |
Fixes: #2 For reference: Namespace the asm! macro: rust-lang/rust#84019 Stablization of the asm! macro: https://github.com/rust-lang/reference/blob/cf3a28145e06a3294/src/inline-assembly.md https://phip1611.de/blog/include-assembler-source-files-in-rust-project-and-build-with-cargo
Expected behavior
Hello! When I clone this repo and run
make create-synthetic-network
and thenmake run-chrome
, I would expect the latter command to build the Docker image and exit successfully per the README.Describe the bug (unexpected behavior)
Instead, when I clone this repo and run
make run-chrome
thedocker build (...)
errors while runningcargo build --release
:Click to expand a shell session of the build and error log
Steps to reproduce
Screenshots
System information
I am not familiar with Rust programming. I found this thread that seems surface-similar to the error I received, and so I thought perhaps it was an architecture-specific problem; I am running on arm64 on an M1 Mac. However I see the same error on an x86 Mac.
OS and arch for both systems:
The text was updated successfully, but these errors were encountered: