I’m trying to install the OS X command line tools, and I’ve tried the beta, and the most recent and nothing is working. Every time I try to use one of the tools something like this happens, my example is make and gnumake as those are what I need right now
-bash: /usr/bin/gnumake: Bad CPU type in executable
-bash: /usr/bin/make: Bad CPU type in executable
note, I am running Yosemite 10.10.4, and my processor is a 2.8 GHz Intel Core i5. If you need any more info be sure to let me know
When macOS tries to run an app that is not built for Apple silicon, macOS will prompt to install Rosetta 2 to automatically translate the app to Apple silicon.
In Terminal, there is no automatic detection for missing Rosetta to run older architecture command line tools.
If you haven’t been prompted for any other app already, manually install Rosetta 2:
softwareupdate --install-rosetta
If you need to run a universal binary in the previous architecture, use arch
and specify the architecture. You need to manually specify the architecture for binaries that need to run other binaries that are not built for Apple silicon, like Homebrew.
arch -x86_64 …
e.g. arch -x86_64 brew install packagename
Alternatively, you can run the entire Terminal app using Rosetta by opening Get Info on Terminal.app in Finder and checking ‘Open using Rosetta’. This way will Terminal and every binary it tries to run through Rosetta, so Apple silicon binaries won’t be supported and performance will be impacted, but you don’t need to specify the architecture to run old binaries.
To switch an existing zsh terminal to x86_64 use this command:
arch -x86_64 zsh
Description
This issue is purely informational (for search engines). macOS 10.15 Catalina can only run 64-bit apps. When downloading an executable from the Releases page, a user may be confused if they only have an Intel CPU, that they may not install the amd64 bit version, and use the 386 version instead. Suggest rename to amd64
to x86_64
in any zip filenames under the Releases tab.
Expected
When I type wsk
in the terminal, it runs
Actual
When I type wsk
in the terminal, it shows the error message bad CPU type in executable: wsk
Steps to reproduce:
- Install macOS 10.15 Catalina (Intel CPU)
- Download the
OpenWhisk_CLI-latest-mac-386.zip
file from
https://github.com/apache/incubator-openwhisk-cli/releases/tag/latest - Unzip the file
- Run
wsk
Workaround
Download the OpenWhisk_CLI-latest-mac-amd64.zip
bundle instead, and run the wsk
executable in there
Suggested Fix
- Rename
OpenWhisk_CLI-latest-mac-amd64.zip
toOpenWhisk_CLI-latest-mac-x86_64.zip
Looks like no one’s replied in a while. To start the conversation again, simply
ask a new question.
Hey guys,
I’m getting this when trying to open an App in Catalina, When I use the GUI it just won’t open, but when I use Terminal it gives me that.
I already tried switching my shell to zsh, but that did nothing.
I noticed the App has a file called osx-intel in it and that’s exactly what I have, so it doesn’t make any sense to get that message when everything seems to be fine.
Any ideas?
Thanks
Mac Pro
Posted on Jan 9, 2020 7:51 AM
jfha28 wrote:
I’m trying to open an App that I have had on my computer for a long time working perfectly fine, but ever since I upgraded to Catalina, the App won’t open, so I tried to open it from the terminal to see if I could get a message of why it doesn’t open and that’s the message I got.
32 bit will not run on Catalina .
You can see list of 32/64 bit apps from
>(option key)System Information>Software>Applications also look at Legacy Software
Posted on Jan 9, 2020 8:22 AM
Similar questions
-
Bad CPU type in executable
I’m trying to run a game on Catalina version 10.15.4 Every time I open it, it closes and Terminal opens giving me the «bad CPU type in executable» error. I’ve already switched the shell to zsh and I’ve opened up System Information to look at the app, and it’s apparently a 64-bit app. So, I’m out of ideas. Any suggestions would be much appreciated. Thank you.
217
2
-
bad CPU type in executable
Hello, I’m trying to run a software called bayenv2 through Terminal on Catalina 10.15.4. I’ve already changed my shell to zsh but still receive:
zsh: bad CPU type in executable
I understand this is an issue with Catalina not supporting 32 bit software like bayenv2. Is there any way to still get this to run? I’ve seen this question before, but none of the answers seemed to be applicable to my situation. I’m not an expert, so apologies if I’m missing something obvious.
1178
1
-
bad CPU type in executable
Hello, I’m trying to run a software called bayenv2 through Terminal on Catalina 10.15.4. I’ve already changed my shell to zsh but still receive:
zsh: bad CPU type in executable
I understand this is an issue with Catalina not supporting 32 bit software like bayenv2. Is there any way to still get this to run? I’ve seen this question before, but none of the answers seemed to be applicable to my situation. I’m not an expert, so apologies if I’m missing something obvious.
473
1
bad CPU type in executable in Catalina
Developers transitioning to M1 Mac and newer processors have repeatedly faced the Bad CPU type error when installing development tools such as Android Studio or the Java SDK.
While this does not necessarily mean that their CPU is unsupported, but is rather linked to changes in the newer processor’s architecture.
You can easily fix this issue within minutes and will not require installing any third-party apps. Just follow alongside me as I lay out the steps.
So, let’s start.
What Causes the Bad CPU Type Error on Mac OS?
The BAD CPU error is seen when you run a 32-bit application on a Mac. Newer versions of Mac OS only support 64-bit apps. Additionally, if you run X86 apps on ARM-based Macs such as the Macbook Air, you will also get this error.
Starting from Mac OS Catalina, Apple decided to drop the support for 32-bit apps. It was announced on October 2019. The last OS to support 32-bit apps was Mojave which was released a year earlier.
Apple informed the developers to transition to the 64-bit starting in 2014. All updates need to be using the newer standard after that period.
You will also encounter the same error if you run applications made for Intel processors in M1 or newer Macs.
Apple transitioned to M1 processors in November 2020. It was now using an architecture similar to the smartphone processors. That meant any existing apps written for the Intel-based Macs would simply not run on the newer models.
Here’s a complete guide on how to check CPU usage on Mac.
To fix the Bad CPU type error on Mac, update your application to the latest version so that it is running 64-bit code. Also, install Rosetta if you are on Mac M1 or later models. This should ensure the application will run correctly.
Here are the methods to fix the Bad CPU type executable error on Mac OS:
Update the App to 64-bit
The App store will show you if your application needs an update. You can select Update All Applications or select the specific app and update it individually.
Before proceeding with the update, google if the 32-bit app you are using received a 64-bit update. If the Developer did not update the app, then you have to use a different method to run the app on your Mac.
Important: Mac OS 10.14 Mojave is the last version that supports 32-bit applications.
Here are the steps to update your app on Mac OS:
Depending on how fast your internet speeds are, the time remaining will be shown. Open the app once the update is finished.
We also fixed the high CPU usage with the kernel task process on Mac OS. Do check it out.
Install Rosetta 2
To run older apps on Apple Silicon-based Macs, you will need Rosetta 2 installed. It translates the instructions present in any application’s code to run on the new processor.
This will enable any old app to run on Mac M1. Code editors, Software SDK, Runtimes, etc. will run flawlessly with Rosetta 2 handling all the translations. But expect the raw performance to be less than an app that is built natively for Apple Silicon.
Follow the steps to install Rosetta 2 on Mac M1 or later:
- Press Command + Space and type Terminal. Click to open it.
- Now type in softwareupdate –install-rosetta and press the Return key.
- Press A when prompted on the Terminal.
You will see the progression of the app as it continues to be installed. A restart is not necessary but will not harm your system if you do it.
Now launch the app you were using earlier. It should work correctly.
Some users have reported the mds_stores process using up their CPU on Mac OS. If you face the same issue check out our separate article.
(Bonus) Emulate an older Mac OS to run the unsupported app
You can run a separate operating system inside your Mac as if it was just another app. It is also known as Virtualization.
Parallels is an app that allows you to run any OS, Windows, Linux, or another version of Mac OS within your Mac. Since you want to run a 32-bit app, install Mac OS Mojave. This supports the old version of the app natively.
Unless the application you are using is critical for your business or operations, move on to a modern app.
A good substitute for the app may be already present in the App Store. If you need the old app specifically, request the Developer to build a 64-bit version or one optimized for Apple Silicon. Then you are guaranteed to use it for years going forward.
Boot Camp is a utility built on Mac to install Windows. Read our detailed guide on how to set up Bootcamp properly and save your precious time from troubleshooting.
Frequently Asked Questions
How to run 32-bit games on Mac?
To run 32-bit apps on Mac, install Mac OS Mojave. Use an external HDD or SSD to store the OS files and games. That way, your existing files on newer Mac OS will remain safe.
How do I run two operating systems on Mac?
By installing the Mac OS on different drives, you can run two instances of Mac OS. They can be the same or different versions. To switch between the OS, use the Startup Disk app and set which volume to use and then restart your Mac.
Final Words
As you saw in the article, a Bad CPU Type error points to a mismatch between the application’s code, operating system version, and the type of processor you are running on your Mac.
And you can easily fix the error with minimal fuss, keeping your main focus on productive work.
That’s all for today. Goodbyes for now.