M1 Mac brew install postgres Error: Cannot install in Homebrew under Rosetta 2 in ARM default prefix (/opt/homebrew)! #10302
Comments
|
I seem to have somehow gotten it back again? But no idea why? I had even restarted shell a few times and ran other arm things to test, no problem, but it was failing. But now after commenting out the check and installing postgres, then uncommenting it out, its back to detecting as arm not intel... Perhaps there's some helpful ways to output potential problem solving steps in those errors better, but I'm unsure how it fixed.. |
|
I'm a little confused about what exactly is going on here, and what's happened since you first posted this issue, but, my guess is that this: has messed up Rosetta/ARM detection. Just to clarify: are you still experiencing this problem or not? Have you resolved all the warnings that |
You did not do this. |
|
I just encountered this issue too. I think the way it manifests, and the associated I also "had a working The issue is I'm now running Initially a wat? moment since I know
It's a Mach-O fat binary so it doesn't matter the architecture of the program that executes it. My impression with
Anyway, primarily commenting for others who encounter this issue via the same route as I did. But also interested in whether shipping fat bottles or providing an option to acquire fat bottles if we don't want to make that the default, would be possible. It would certainly solve the whole coexistence issue. |
|
I opened a feature suggestion: #10307 |
|
@MikeMcQuaid might I suggest we reopen this for further examination: Homebrew/discussions#412 (reply in thread). This might actually be a bug where, when homebrew is running in a translated environment, it thinks it's on an Intel Mac and doctor overzealously suggests it's not installed in the right prefix. I think the desired behavior should be that even when running translated, brew still installs aarch64e binaries to the cellar under |
If that's the case and it reproducible instructions can be provided using only Homebrew (not Cask) and macOS provided software: please open a new issue detailing it and we'll consider working on a fix.
If this is the main cause of the problem: the workaround/solution is likely "don't do that". We'll review PRs to do differently, though. |
Bug report
brew updateand can still reproduce the problem?brew doctor, fixed all issues and can still reproduce the problem?brew configandbrew doctorand included their output with your issue?What you were trying to do (and why)
brew install postgres
What happened (include command output)
Command output
What you expected to happen
Installed postgres, which worked until a day ago, somehow brew now things I'm
CPU.intel?is true.Output of
brew configandbrew doctorcommandsI did try stashing homebrew directory and reinstalling it from github. I tried several different ruby installs.
Any reason why suddenly
Hardware::CPU.intel?would be returning true when I'm on an ARM mac?Edit: Actually I checked those flags and all return false (now?), I tried disabling that check and install seems to work fine, now I'll try resetting things and running again...
The text was updated successfully, but these errors were encountered: