Can't built main on M1

[buffalu]

Sup mango team.

I can't build on main right now, seems like something wrong with switchboard dependency. This only happens on M1. If I sync to a build server + build, its okay

   Compiling switchboard-utils v0.1.29
error[E0080]: evaluation of constant value failed
  --> /Users/.../.cargo/registry/src/github.com-1ecc6299db9ec823/switchboard-utils-0.1.29/src/lib.rs:19:18
   |
19 | #[derive(Default,AsBytes,FromBytes,Clone,Debug)]
   |                  ^^^^^^^ attempt to divide `1_usize` by zero
   |
   = note: this error originates in the derive macro `AsBytes` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0080`.
error: could not compile `switchboard-utils` due to previous error
warning: build failed, waiting for other jobs to finish...
error: build failed

mango-v3 % rustup --version
rustup 1.24.3 (ce5817a94 2021-05-31)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.59.0-nightly (207c80f10 2021-11-30)`

% rustc --version
rustc 1.59.0-nightly (207c80f10 2021-11-30)

[mschneider]

please use rustc 1.57.0-nightly (fdf65053e 2021-09-07)

…

On Wed, Dec 1, 2021 at 6:13 AM buffalu ***@***.***> wrote: Sup mango team. I can't build on main right now, seems like something wrong with switchboard dependency. Compiling switchboard-utils v0.1.29 error[E0080]: evaluation of constant value failed --> /Users/.../.cargo/registry/src/github.com-1ecc6299db9ec823/switchboard-utils-0.1.29/src/lib.rs:19:18 | 19 | #[derive(Default,AsBytes,FromBytes,Clone,Debug)] | ^^^^^^^ attempt to divide `1_usize` by zero | = note: this error originates in the derive macro `AsBytes` (in Nightly builds, run with -Z macro-backtrace for more info) For more information about this error, try `rustc --explain E0080`. error: could not compile `switchboard-utils` due to previous error warning: build failed, waiting for other jobs to finish... error: build failed mango-v3 % rustup --version rustup 1.24.3 (ce5817a94 2021-05-31) info: This is the version for the rustup toolchain manager, not the rustc compiler. info: The currently active `rustc` version is `rustc 1.59.0-nightly (207c80f10 2021-11-30)` % rustc --version rustc 1.59.0-nightly (207c80f10 2021-11-30) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#84>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABDF7GYZCNJHGIADVSXS23UOWVGJANCNFSM5JDRDMSA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[dafyddd]

I think the solana compiler comes with a rustc. And I use solana-cli 1.8 to compile and don't have any issues.

[bolerap]

same error, I also tried with rustc 1.57.0-nightly (2021-09-07) same error. What wrong with me?

[microwavedcola1]

@thanhngvpt @buffalu are you guys using rosetta compatibility mode? m1 is my main driver, and havent had any issues so far

[RohanKapurDEV]

havent had any issues building on m1 either

[sthornington]

The root cause of this is that mango (and switchboard) have #[repr(C)] for some account data structs (SwitchboardDecimal, *Node in matching.rs and *Event in queue.rs), but on ARM, the alignment of i128 is 16 bytes, vs 8 bytes for x86_64. These structs should all be #[repr(packed)] in my opinion, as they are in the serum dex examples.

[sthornington]

In fact, it looks like SwitchboardDecimal is already packed in the latest...

[sthornington]

@ckamm did you have any luck upgrading switchboard? I see you pinned the versions to older ones fairly recently...

[ckamm]

Upgrading switchboard wasn't a priority so I haven't looked at it further. This PR has an upgrade though: #150

[sthornington]

Gotcha. Yeah I haven’t gotten further enough to see whether switching all the account state structs to repr(packed) fixes everything else. I suspect one day everyone will be forced to switch to proper serdes using borsh rather than bytemuck casting.

[smu160]

I ran into the same issue, and I was able to rectify the issue with rustup by switching the active tool-chain.

You can confirm by running: rustup show. If you see stable-x86_64-apple-darwin (default) under active toolchain, you're good to go.

Otherwise, do as follows:

rustup default stable-x86_64-apple-darwin

Try it out:

cargo build

You should be able to build without any platform specific issues now.

[sthornington]

Yes of course you can fix an issue with bad alignment on ARM by not compiling on ARM. 😀

[namnh06]

I've got the same issue with Ubuntu 20.04