Then use that prefix again when installing programs with the old version of homebrew: arch -x86_64 brew install. To install the second version of brew (using Rosetta) use arch -x86_64 as a prefix to the installation command ( source). Option 2: Using one iTerm application, but two versions of homebrew I copied the app successfully, but couldn’t get the two versions of homebrew to coexist. Then install homebrew from the iTerm Rosetta app, and any incompatible programs.ĭefault to using your standard iTerm app when installing programs, and use the iTerm Rosetta app when installing programs that have compatibility issues. To create your second iTerm app, copy your iTerm app, name it “iTerm rosetta” version, and launch it using Rosetta. Option 1: Using two versions of iTerm (one using the M1 architecture, one using Rosetta): There are two main approaches to a dual setup, neither of which I could get to work, but you may be able to! I’ve included a conceptual overview of both for context If you want to take advantage of the M1 software where possible, some solutions on the internet also suggest that it’s possible to run a dual setup, so that you can install M1-compatible software on the M1 architecture, and then have a backup way to install non-compatible software (like dbt). Granted, using this approach unilaterally means that I lose some of the speedups from the M1 chip, and some programs are compatible with the M1 chip. This let me install dbt without issues, and all my other programs Reinstalled homebrew using my (Rosetta) iTerm To do this: right-click on iTerm, click ‘Get Info’, and check the ‘Open using Rosetta’ option. This is a way to use programs as though they are operating on an non-M1 Mac I can’t remember the exact instructions here, but think this was pretty google-able I personally was finding that I had M1 issues on other programs installed via homebrew (pyenv, ruby, everything, gah!) that a python env wouldn’t solve, so I had to do something a little more drastic!Ĭompletely uninstalled homebrew, and all brew-installed programs Step 6: Deactivate your virtual environment.Īnd that’s it! Hope this saves some time for anyone struggling through the same situationĬhiming in here with my suggestions! (Thanks for the tag of all, if dbt is the only command line program you are having issues with, use Olya’s approach! It’s great! Step 5: Do whatever you need to do in dbt! Step 4: Change your working directory, if necessary. Python3 -m pip install -user -upgrade pip Step 3: Create a python virtual environment and install dbt.įull instructions here, but run these are the exact commands I ran in the Terminal: *Per - you may also consider uninstalling Homebrew completely and reinstalling brew via Rosetta first. Then, if you run which dbt you should get dbt not found. I’m team Homebrew - run brew uninstall dbt in the Terminal*. Step 2: Open your Terminal and uninstall any versions of dbt you may have tried to install before. Go to Applications > Utilities > Terminal (or go to whatever other Terminal app you use), right click, select ‘Get Info’ and then select ‘Open using Rosetta’ under the General options. Step 1: Set up your Terminal to use Rosetta. Screen Shot at 2.21.12 PM 886×150 45.4 KBĪfter some searching of the interwebs, I found a solution that worked for me, tucked away in a GitHub issue, in a comment by from Mike Lanza (thanks Mike! none of the other mentioned workarounds worked for me ).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |