Skip to content
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

Jump to bottom

"Error: Only 64-bit Intel and M1 processors are supported on OS X" on M1 pro #11838

Open
holmrenser opened this issue Jan 6, 2022 · 4 comments · May be fixed by #11975
Open

"Error: Only 64-bit Intel and M1 processors are supported on OS X" on M1 pro #11838

holmrenser opened this issue Jan 6, 2022 · 4 comments · May be fixed by #11975
Labels
confirmed good first issue Impact:few Project:Apple

Comments

@holmrenser
Copy link

@holmrenser holmrenser commented Jan 6, 2022 •
edited

I'm on a 14" macbook M1 pro and get the following error when trying to run a freshly downloaded/installed meteor 2.5.3:

Error: Only 64-bit Intel and M1 processors are supported on OS X

From the blogpost announcing meteor 2.5.1 I would expect meteor to work on my machine.
Given that I'm on an M1, the error message saying only intel and M1 is supported is not very helpful.

UPDATE:
Following the code checking machine info, at https://github.com/meteor/meteor/blob/devel/tools/utils/archinfo.ts#L161-L163 there is a check whether uname -p returns arm.

On my machine uname -p returns arm64, in addition sysctl -n hw.cpu64bit_capable returns 1, causing the checks to fail.

UPDATE2:
I now realize that I am using uname as provided by gnu coreutils (installed through homebrew). If I use the original uname that comes with MacOS uname -p returns the correct arm. Homebrew gnu coreutils uname -p returns arm64.

Perhaps a bit of an edge case, nonetheless a situation I would expect to arise more often (it is not uncommon to install gnu coreutils on mac). I can submit a PR if desired.
@holmrenser
Copy link
Author

@holmrenser holmrenser commented Jan 6, 2022

Thanks for the comment. I am on a fresh machine and haven't used meteor on this machine before (so no rosetta terminal etc.). I have tried both the 'old' way of installing meteor and installing globally with npm, both result in the same problem.

In the update of my original issue you can see what I think is the problem, which is in the way meteor checks what hardware it is running on.

@StorytellerCZ StorytellerCZ added the Project:Apple label Jan 13, 2022
@renanccastro
Copy link
Contributor

@renanccastro renanccastro commented Jan 24, 2022

Thanks for your report @holmrenser.
I don't think this issue will be a usual one, and even then there is a workaround as you've said in your thread.
Are you willing to write a PR? We would gladly merge it.

It's even a good first-time issue, so I will update the tags.

@renanccastro renanccastro added confirmed good first issue Impact:few labels Jan 24, 2022
@holmrenser
Copy link
Author

@holmrenser holmrenser commented Jan 25, 2022

Indeed probably not a frequent issue, but OTOH might also not be very uncommon (I think gnu core-utils is used frequently on mac: 75K installs in the last 30days). I'll draft a PR later today!

@jakobbouchard
Copy link

@jakobbouchard jakobbouchard commented Feb 15, 2022

Just chiming in to say that I ran into the same issue. I temporarily fixed it by making the origin uname the default one instead.

@ptorre9475 ptorre9475 mentioned this issue Mar 9, 2022
Open
@StorytellerCZ StorytellerCZ linked a pull request Apr 2, 2022 that will close this issue
for issue 11838 #11975
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
confirmed good first issue Impact:few Project:Apple
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

for issue 11838 riseth/meteor
4 participants
@StorytellerCZ @renanccastro @holmrenser @jakobbouchard