M1 Mac build issue - could not compile wabt-sys

[krpeacock]

Issue can be observed in any example project, or even a blank ts entrypoint. Spec is
OS: Monterey 12.3.1
Processor: M1 Pro
Node: 16.14.0
Rust: 1.60.0

Full output is:

   Compiling wabt v0.10.0
error: failed to add native library /var/folders/xt/9tbb8ws541979mzdx2n9ms2r0000gn/T/cargo-installtXfSMj/release/build/wabt-sys-e78371680e273395/out/build/libwabt.a: file too small to be an archive

error: could not compile `wabt-sys` due to previous error
warning: build failed, waiting for other jobs to finish...
error: failed to compile `ic-cdk-optimizer v0.3.4`, intermediate artifacts can be found at `/var/folders/xt/9tbb8ws541979mzdx2n9ms2r0000gn/T/cargo-installtXfSMj`
Caused by:
  build failed
Error: Command failed: cd target/azle && cargo install ic-cdk-optimizer --root ..
    at checkExecSyncError (node:child_process:828:11)
    at execSync (node:child_process:902:15)
    at installRustDependencies (/Users/kyle/code/azle-rss/backend/node_modules/azle/src/azle.ts:60:13)
    at azle (/Users/kyle/code/azle-rss/backend/node_modules/azle/src/azle.ts:26:5)
    at Object.<anonymous> (/Users/kyle/code/azle-rss/backend/node_modules/azle/src/azle.ts:15:1)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Module.m._compile (/Users/kyle/code/azle-rss/backend/node_modules/ts-node/src/index.ts:1365:23)
    at Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
    at Object.require.extensions.<computed> [as .ts] (/Users/kyle/code/azle-rss/backend/node_modules/ts-node/src/index.ts:1368:12)
    at Module.load (node:internal/modules/cjs/loader:981:32) {
  status: 101,
  signal: null,
  output: [ null, null, null ],
  pid: 97782,
  stdout: null,
  stderr: null
}
Error: The build step failed for canister 'rrkah-fqaaa-aaaaa-aaaaq-cai' with an embedded error: The custom tool failed.

[lastmjs]

Related: https://forum.dfinity.org/t/setup-internet-identity-locally-failed-macbook-m1/7684

[lastmjs]

Related: dfinity/internet-identity#434

[lastmjs]

Are you able to compile and run ic-cdk-optimizer outside of Azle?

[lastmjs]

As a quick local fix you might try commenting this out: https://github.com/demergent-labs/azle/blob/main/src/azle.ts#L104 in node_modules/azle/src/azle.ts

[lastmjs]

Related: pepyakin/wabt-rs#78

[lastmjs]

Someone else ran into an issue on an M1 with swc, adding this for future reference. FYI I don't have easy access to an M1 nor do any members of my team, so I'm not sure what I can do but try to help someone with an M1 figure this out. I might have a friend who can help in the future but no guarantees.

[krpeacock]

I'm sure there's some single command that magically fixes it somewhere. I'm not blocked because I have other machines though

[cryptoisgood]

@krpeacock I wrapped dfx and the azle dependencies in a docker container. It's not really ready to be used but it be cool if you tried it to see if it gets you past this issue.

https://www.npmjs.com/package/wdfx

[infu]

2min fix for M1

1. Install ic-cdk-optimizer standalone.

 cargo install ic-cdk-optimizer

2. Remove dependency install from

   azle/src/azle.ts

   Line 60 in 83090ff

   execSync(

    // execSync(
    //     `cd target/azle && cargo install ic-cdk-optimizer --root ..`,
    //     { stdio: 'inherit' }
    // );

3. Change path to ic-cdk-optimiser

   azle/src/azle.ts

   Line 105 in 83090ff

   `./target/bin/ic-cdk-optimizer ./target/wasm32-unknown-unknown/release/${canisterName}.wasm -o ./target/wasm32-unknown-unknown/release/${canisterName}.wasm`,

execSync(
        `~/.cargo/bin/ic-cdk-optimizer ./target/wasm32-unknown-unknown/release/${canisterName}.wasm -o ./target/wasm32-unknown-unknown/release/${canisterName}.wasm`,
        { stdio: 'inherit' }
    );

[lastmjs]

Thanks for this, we can probably get this fix into Azle soon. @krpeacock I would love to know if this works for you if you ever get a chance.

[lastmjs]

Could someone with an M1 could test building and deploying with npm install [email protected]? If that works then the issue should be resolved and we can get this into a major release.

[lastmjs]

I've had one person successfully use Azle on an M1 with this fix, so I'm considering it fixed for now

[lastmjs]

I'm hoping this will for sure be resolved once we switch Azle to ic-wasm, like we are planning to do in Kybra: demergent-labs/kybra#42