Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Big Sur / M1 Mac support #1182

Open
jnordberg opened this issue Jul 28, 2021 · 3 comments
Open

Big Sur / M1 Mac support #1182

jnordberg opened this issue Jul 28, 2021 · 3 comments

Comments

@jnordberg
Copy link

Trying to install the toolchain using homebrew on a m1 mac results in:

eosio.cdt: The intel architecture is required for this software.
Error: An unsatisfied requirement failed this build.

Alternatively trying to install it using a separate brew install that's run under rosetta 2 results in:

Error: An exception occurred within a child process:
  RuntimeError: Error, only supporting binary packages at this time

And finally building from source results in:

ld: framework not found Foundation
@kj4ezj
Copy link
Contributor

kj4ezj commented Jul 28, 2021

Thank you for reaching out! Unfortunately, EOSIO has never officially supported the ARM architecture.

Formal M1 support would not only require a working build targeting ARM, but also M1 support by all of our test infrastructure and an M1-based buildfleet to be built out. In particular, Anka (a docker-like type 2 hypervisor we use for macOS virtualization in our CI system) is a key vendor who has yet to add ARM/M1 support.

We are paying close attention to the adoption of ARM in PCs and datacenters by Apple, OEMs, chipmakers, and cloud providers.

@bogniq
Copy link
Collaborator

bogniq commented Jul 29, 2021

The ld: framework not found Foundation error is related with #1005

@aclark-b1
Copy link

Duplicate of EOSIO/eos#9849

@aclark-b1 aclark-b1 marked this as a duplicate of EOSIO/eos#9849 Aug 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants