Bug: doesn't compile on Apple M1? #41

pedropuchalski · 2023-10-10T20:52:14Z

Describe the bug

After running compilation on rust level, that can be ivoced also by npm run build command after downloading sources from git, I get:
`...
Compiling cipher v0.4.4
error: failed to build archive: 'wasm32.o': section too large

The following warnings were emitted during compilation:

warning: warning: /Library/Developer/CommandLineTools/usr/bin/ranlib: archive library: /Users/(...)/surrealdb.wasm/target/wasm32-unknown-unknown/release/build/psm-e7fd6e39c2c90a79/out/libpsm_s.a the table of contents is empty (no object file members in the library define global symbols)

error: could not compile psm (lib) due to previous error
warning: build failed, waiting for other jobs to finish...
Error: Compiling your crate to WebAssembly failed
Caused by: Compiling your crate to WebAssembly failed
Caused by: failed to execute cargo build: exited with exit status: 101
full command: cd "/Users/pedropuchalski/Documents/praca/FirmaNext/sceneMgm/surrealdb.wasm" && "cargo" "build" "--lib" "--release" "--target" "wasm32-unknown-unknown" "--no-default-features" "--features" "protocol-ws,protocol-http,kv-indxdb,kv-mem,rustls"`

Steps to reproduce

Try to compile on Apple MacBook Air with M1, Ventura.

Expected behaviour

Compiled *.wasm file.

SurrealDB version

"1.0.0", default-features = false

Contact Details

[email protected]

Is there an existing issue for this?

I have searched the existing issues

Code of Conduct

I agree to follow this project's Code of Conduct

The text was updated successfully, but these errors were encountered:

bambooyuh · 2023-10-12T18:22:19Z

I have a near identical issue with M1 chip on Sonoma

Luxbit · 2023-10-19T03:48:01Z

You need to manually set AR and CC.
If you installed LLVM via homebrew, add this to your env:

echo 'export AR=/opt/homebrew/opt/llvm/bin/llvm-ar' >> ~/.zshrc
echo 'export CC=/opt/homebrew/opt/llvm/bin/clang' >> ~/.zshrc

Also make sure to run cargo clean before rebuilding

bambooyuh · 2023-10-19T05:43:20Z

Thank you. This worked.

bambooyuh · 2023-10-19T18:55:55Z

Except now I'm getting this error, which seems to be related...

error: failed to run custom build command for ring v0.16.20

--- stdout
OPT_LEVEL = Some("0")
TARGET = Some("aarch64-apple-darwin")
HOST = Some("aarch64-apple-darwin")
cargo:rerun-if-env-changed=CC_aarch64-apple-darwin
CC_aarch64-apple-darwin = None
cargo:rerun-if-env-changed=CC_aarch64_apple_darwin
CC_aarch64_apple_darwin = None
cargo:rerun-if-env-changed=HOST_CC
HOST_CC = None
cargo:rerun-if-env-changed=CC
CC = Some("/opt/homebrew/opt/llvm/bin/clang")
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("true")
cargo:rerun-if-env-changed=CFLAGS_aarch64-apple-darwin
CFLAGS_aarch64-apple-darwin = None
cargo:rerun-if-env-changed=CFLAGS_aarch64_apple_darwin
CFLAGS_aarch64_apple_darwin = None
cargo:rerun-if-env-changed=HOST_CFLAGS
HOST_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = None

--- stderr
running "/opt/homebrew/opt/llvm/bin/clang" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-2" "-fno-omit-frame-pointer" "--target=arm64-apple-darwin" "-I" "include" "-Wall" "-Wextra" "-std=c1x" "-Wbad-function-cast" "-Wnested-externs" "-Wstrict-prototypes" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-gfull" "-DNDEBUG" "-c"
In file included from crypto/fipsmodule/aes/aes_nohw.c:17:
In file included from crypto/fipsmodule/aes/../../internal.h:114:
include/GFp/check.h:27:11: fatal error: 'assert.h' file not found
27 | # include <assert.h>
| ^~~~~~~~~~
1 error generated.

bambooyuh · 2023-11-10T07:21:58Z

@Luxbit

After the ring update I'm still getting a similar error as posted above.

Using a Mac m1 chip.

warning: [email protected]: error: unable to create target: 'No available targets are compatible with triple "wasm32-unknown-unknown"'
warning: [email protected]: 1 error generated.

error: failed to run custom build command for ring v0.17.5

Luxbit · 2023-11-10T17:43:03Z

@roachj9 Sorry, but I can't reproduce this issue. Everything compiles fine for me using rustc 1.71.0 (8ede3aae2 2023-07-12) on M1 running macOS 13.6.1 (22G313)

Korolen · 2023-12-17T01:33:22Z

Documenting my experience. On M1 Pro, MacOS 12.5.1

Initially I had the same error as @roachj9.

Now, after setting the flags and cleaning, I'm stuck on:

cargo build --target wasm32-unknown-unknown --release
   Compiling proc-macro2 v1.0.70
.......
   Compiling unicode-normalization v0.1.22
error: failed to run custom build command for `psm v0.1.21`

Caused by:
  process didn't exit successfully: `/Users/tom/c/rs-bench-compile-times-surreal-dioxus/target/release/build/psm-620eb07fafc6a24c/build-script-build` (exit status: 1)
  --- stdout
  OPT_LEVEL = Some("3")
  TARGET = Some("wasm32-unknown-unknown")
  HOST = Some("aarch64-apple-darwin")
  cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
  CC_wasm32-unknown-unknown = None
  cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
  CC_wasm32_unknown_unknown = None
  cargo:rerun-if-env-changed=TARGET_CC
  TARGET_CC = None
  cargo:rerun-if-env-changed=CC
  CC = Some("/opt/homebrew/opt/llvm/bin/clang")
  cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
  CFLAGS_wasm32-unknown-unknown = None
  cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
  CFLAGS_wasm32_unknown_unknown = None
  cargo:rerun-if-env-changed=TARGET_CFLAGS
  TARGET_CFLAGS = None
  cargo:rerun-if-env-changed=CFLAGS
  CFLAGS = None
  cargo:rustc-cfg=asm
  cargo:rustc-cfg=switchable_stack
  cargo:rerun-if-env-changed=AR_wasm32-unknown-unknown
  AR_wasm32-unknown-unknown = None
  cargo:rerun-if-env-changed=AR_wasm32_unknown_unknown
  AR_wasm32_unknown_unknown = None
  cargo:rerun-if-env-changed=TARGET_AR
  TARGET_AR = None
  cargo:rerun-if-env-changed=AR
  AR = Some("/opt/homebrew/opt/llvm/bin/llvm-ar")
  cargo:rerun-if-env-changed=ARFLAGS_wasm32-unknown-unknown
  ARFLAGS_wasm32-unknown-unknown = None
  cargo:rerun-if-env-changed=ARFLAGS_wasm32_unknown_unknown
  ARFLAGS_wasm32_unknown_unknown = None
  cargo:rerun-if-env-changed=TARGET_ARFLAGS
  TARGET_ARFLAGS = None
  cargo:rerun-if-env-changed=ARFLAGS
  ARFLAGS = None
  running: ZERO_AR_DATE="1" "/opt/homebrew/opt/llvm/bin/llvm-ar" "cq" "/Users/tom/c/rs-bench-compile-times-surreal-dioxus/target/wasm32-unknown-unknown/release/build/psm-78afdcbbd9743968/out/libpsm_s.a" "src/arch/wasm32.o"

  --- stderr


  error occurred: Failed to find tool. Is `` installed?


warning: build failed, waiting for other jobs to finish...

This is with a repo that has nothing but cargo init and adding this git repo by URL with, in Cargo.toml:

[dependencies]
surrealdb = { git = "https://github.com/surrealdb/surrealdb.wasm", branch = "main"<<this didn't help either: , default-features = false>> }

Maybe it's unrelated to being on M1, though I do notice it's the same psm crate that's generating the error, still.

DrewRidley · 2024-09-06T16:51:32Z

Hi all,

The issue can still be reproduced on an M3 Pro.

echo 'export AR=/opt/homebrew/opt/llvm/bin/llvm-ar' >> ~/.zshrc
echo 'export CC=/opt/homebrew/opt/llvm/bin/clang' >> ~/.zshrc

With homebrew installed LLVM seems to have fixed the issue. There is a weird side-effect where it no longer caches SurrealDB, and has to rebuild it on every incremental change.

Any solutions to this would be much appreciated!

dfesmp · 2024-12-22T18:30:58Z

I'm on windows 10 facing the same issue. Works fine on linux.

Steps to reproduce (assuming you have rust installed):

install llvm: choco install llvm
install leptos and start a template ssr project:

cargo install cargo-leptos
cargo leptos new --git https://github.com/leptos-rs/start-axum

add surrealdb as dependency on Cargo.toml:

[package]
name = "my-web"
version = "0.1.0"
edition = "2021"

[lib]
crate-type = ["cdylib", "rlib"]

[dependencies]
axum = { version = "0.7", optional = true }
chrono = "0.4.38"
console_error_panic_hook = "0.1"
http = "1"
leptos = { version = "0.7.0" }
leptos_axum = { version = "0.7.0", optional = true }
leptos_meta = { version = "0.7.0" }
leptos_router = { version = "0.7.0" }
# extra dependency, same error with just surrealdb = "2.1.3"
surrealdb = { version = "2.1.3", default-features = false, features = ["protocol-ws"], package = "surrealdb-nightly" }
thiserror = "1"
tokio = { version = "1", features = ["rt-multi-thread"], optional = true }
tower = { version = "0.4", optional = true }
tower-http = { version = "0.5", features = ["fs"], optional = true }
wasm-bindgen = "=0.2.99"

[features]
hydrate = ["leptos/hydrate"]
ssr = [
    "dep:axum",
    "dep:tokio",
    "dep:tower",
    "dep:tower-http",
    "dep:leptos_axum",
    "leptos/ssr",
    "leptos_meta/ssr",
    "leptos_router/ssr",
]

# Defines a size-optimized profile for the WASM bundle in release mode
[profile.wasm-release]
inherits = "release"
opt-level = 'z'
lto = true
codegen-units = 1
panic = "abort"
...

try to run with cargo leptos watch

The following warnings were emitted during compilation:

warning: [email protected]: error: unable to create target: 'No available targets are compatible with triple "wasm32-unknown-unknown"'
warning: [email protected]: 1 error generated.

error: failed to run custom build command for `ring v0.17.8`

Caused by:
  process didn't exit successfully: `C:\Users\.....\my-web\target\front\debug\build\ring-661c2665f5b6d7a3\build-script-build` (exit code: 1)
  --- stdout
  cargo:rerun-if-env-changed=RING_PREGENERATE_ASM
  cargo:rustc-env=RING_CORE_PREFIX=ring_core_0_17_8_
  OPT_LEVEL = Some(0)
  OUT_DIR = Some(C:\Users\.....\my-web\target\front\wasm32-unknown-unknown\debug\build\ring-8ae652aa7f608cc2\out)
  TARGET = Some(wasm32-unknown-unknown)
  HOST = Some(x86_64-pc-windows-msvc)
  cargo:rerun-if-env-changed=CC_wasm32-unknown-unknown
  CC_wasm32-unknown-unknown = None
  cargo:rerun-if-env-changed=CC_wasm32_unknown_unknown
  CC_wasm32_unknown_unknown = None
  cargo:rerun-if-env-changed=TARGET_CC
  TARGET_CC = None
  cargo:rerun-if-env-changed=CC
  CC = None
  cargo:rerun-if-env-changed=CC_ENABLE_DEBUG_OUTPUT
  RUSTC_WRAPPER = None
  cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some(true)
  cargo:rerun-if-env-changed=CFLAGS_wasm32-unknown-unknown
  CFLAGS_wasm32-unknown-unknown = None
  cargo:rerun-if-env-changed=CFLAGS_wasm32_unknown_unknown
  CFLAGS_wasm32_unknown_unknown = None
  cargo:rerun-if-env-changed=TARGET_CFLAGS
  TARGET_CFLAGS = None
  cargo:rerun-if-env-changed=CFLAGS
  CFLAGS = None
  CARGO_ENCODED_RUSTFLAGS = Some()
  cargo:warning=error: unable to create target: 'No available targets are compatible with triple "wasm32-unknown-unknown"'
  cargo:warning=1 error generated.

  --- stderr


  error occurred in cc-rs: Command "clang" "-O0" "-ffunction-sections" "-fdata-sections" "-fno-exceptions" "-g" "-fno-omit-frame-pointer" "--target=wasm32-unknown-unknown" "-I" "include" "-I" "C:\\Users\\.....\\my-web\\target\\front\\wasm32-unknown-unknown\\debug\\build\\ring-8ae652aa7f608cc2\\out" "-Wall" "-Wextra" "-fvisibility=hidden" "-std=c1x" "-Wall" "-Wbad-function-cast" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wnested-externs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wstrict-prototypes" "-Wundef" "-Wuninitialized" "-g3" "-nostdlibinc" "-DNDEBUG" "-DRING_CORE_NOSTDLIBINC=1" "-o" "C:\\Users\\.....\\my-web\\target\\front\\wasm32-unknown-unknown\\debug\\build\\ring-8ae652aa7f608cc2\\out\\172e8fe49fe517e0-curve25519.o" "-c" "crypto/curve25519/curve25519.c" with args clang did not execute successfully (status code exit code: 1).


warning: build failed, waiting for other jobs to finish...
      Notify watching paths src, style, public
      Leptos ctrl-c received

dfesmp · 2024-12-22T19:16:59Z

In case it helps anyone: for my use case I can just serve the app from wsl

pedropuchalski added the bug Something isn't working label Oct 10, 2023

rushmorem mentioned this issue Jan 24, 2024

Bug: dependency ring cannot target wasm32_unknown_unknown surrealdb/surrealdb#3321

Closed

2 tasks

johnnynanjiang mentioned this issue Jun 11, 2024

Apple M1: dfx deploy failed with errors container state improper adrian-d-hidalgo/azle-api-rest-nextjs#8

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bug: doesn't compile on Apple M1? #41

Bug: doesn't compile on Apple M1? #41

pedropuchalski commented Oct 10, 2023

bambooyuh commented Oct 12, 2023

Luxbit commented Oct 19, 2023 •

edited

Loading

bambooyuh commented Oct 19, 2023

bambooyuh commented Oct 19, 2023

bambooyuh commented Nov 10, 2023

Luxbit commented Nov 10, 2023

Korolen commented Dec 17, 2023 •

edited

Loading

DrewRidley commented Sep 6, 2024

dfesmp commented Dec 22, 2024 •

edited

Loading

dfesmp commented Dec 22, 2024

Bug: doesn't compile on Apple M1? #41

Bug: doesn't compile on Apple M1? #41

Comments

pedropuchalski commented Oct 10, 2023

Describe the bug

Steps to reproduce

Expected behaviour

SurrealDB version

Contact Details

Is there an existing issue for this?

Code of Conduct

bambooyuh commented Oct 12, 2023

Luxbit commented Oct 19, 2023 • edited Loading

bambooyuh commented Oct 19, 2023

bambooyuh commented Oct 19, 2023

bambooyuh commented Nov 10, 2023

Luxbit commented Nov 10, 2023

Korolen commented Dec 17, 2023 • edited Loading

DrewRidley commented Sep 6, 2024

dfesmp commented Dec 22, 2024 • edited Loading

dfesmp commented Dec 22, 2024

Luxbit commented Oct 19, 2023 •

edited

Loading

Korolen commented Dec 17, 2023 •

edited

Loading

dfesmp commented Dec 22, 2024 •

edited

Loading