Can't run the installation script on M1 Pro
Hi,
I'm trying to run the curl -sSL https://get.wasp-lang.dev/installer.sh | sh on my mac's terminal but it gives me the following error :
Do you have an idea ?
From the repo and script it shows a version of wasp that doesn't seems to be compatible with my setup ?!
Thank you !
2 Replies
Hi @gymooorr. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information provided in the knowledge sources, it appears that you're encountering an issue related to running Wasp on a Mac with an M1 Pro chip, which uses the arm64 architecture. Here's what you need to know:
1. Wasp currently doesn't have a prebuilt binary package specifically for arm64 (Apple Silicon) Macs. The existing binary is built for x86_64 architecture.
2. To run Wasp on an M1 Pro (arm64) Mac, you need to install Rosetta 2, which allows you to run applications designed for x86 on arm64 (Apple Silicon) devices.
To resolve this issue, follow these steps:
1. Install Rosetta 2 on your Mac by running the following command in your terminal:
2. After installing Rosetta 2, try running the Wasp installation script again:
This should allow you to install and run Wasp on your M1 Pro Mac.
For more information, you can refer to the Wasp Quick Start guide, which mentions this specific issue for Macs with Apple Silicon.
It's worth noting that the Wasp team is aware of this limitation and is planning to add support for arm64 Macs in the future. There's an open GitHub issue discussing the addition of macOS arm64 binary packages to their releases, which you can follow for updates on this matter.
GitHub Issue: Add macOS arm64 binary package
If you continue to experience issues after following these steps, please provide more details about the specific error you're encountering.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @gymooorr, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
Hey @gymooorr did the bot's answer solve your problem. This was the solution I would have suggested as well.