Homebrew
I no longer can get Homebrew to function, zsh: command not found: brew #5259
Replies: 11 comments 28 replies
-
|
What does |
Beta Was this translation helpful? Give feedback.
-
|
You can see an entry for each time that I have entered the commands to pull “activate” Homebrew.
However, there is no ORIGINAL version in .zprofile.pysave if that means anything. Just something for Python 3.8 and 3.9.
# Setting PATH for Python 3.11
# The original version is saved in .zprofile.pysave
PATH="/Library/Frameworks/Python.framework/Versions/3.11/bin:${PATH}"
export PATH
eval $(/opt/homebrew/bin/brew shellenv)
eval $(/opt/homebrew/bin/brew shellenv)
eval $(/opt/homebrew/bin/brew shellenv)
eval "$(/opt/homebrew/bin/brew shellenv)"
eval $(/opt/homebrew/bin/brew shellenv)
eval "$(/opt/homebrew/bin/brew shellenv)"
eval $(/opt/homebrew/bin/brew shellenv)
eval "$(/opt/homebrew/bin/brew shellenv)"
eval $(/opt/homebrew/bin/brew shellenv)
eval "$(/opt/homebrew/bin/brew shellenv)"
… On Apr 4, 2024, at 1:38 PM, Sean Molenaar ***@***.***> wrote:
What does cat ~/.zprofile say regarding Homebrew?
—
Reply to this email directly, view it on GitHub <#5259 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM4R6IQ5VCXXX3ZVDFXDFOLY3WM3LAVCNFSM6AAAAABFXZDQ42VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TAMJTGM2TE>.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
|
So does this need to become a brew issue, it feels like brew is broken. |
Beta Was this translation helpful? Give feedback.
-
|
Brew is fine, you're just in a curious situation where your shell environment is not working. What happens if you reduce all those eval lines in |
Beta Was this translation helpful? Give feedback.
-
|
I do not know why it would have stopped working suddenly. It continues to work on Ventura.
As per your request:
% bash list
bash: list: No such file or directory
% echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin
… On Apr 5, 2024, at 2:41 AM, Sean Molenaar ***@***.***> wrote:
Brew is fine, you're just in a curious situation where your shell environment is not working.
What happens if you reduce all those eval lines in ~/.zprofile to just one and then reboot your Mac. If it doesn't work after, let me know what echo $PATH says.
—
Reply to this email directly, view it on GitHub <#5259 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM4R6IURHP3MXALGHUH3HHTY3ZISHAVCNFSM6AAAAABFXZDQ42VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TAMJYGIYDE>.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
|
I also tried changing the path directly:
export PATH=$PATH/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/opt/homebrew/bin/
And entered it into .zshrc; however; it has no effect.
But it does as a direct command line entry from terminal (one session only) just like the other commands.
… On Apr 5, 2024, at 2:41 AM, Sean Molenaar ***@***.***> wrote:
Brew is fine, you're just in a curious situation where your shell environment is not working.
What happens if you reduce all those eval lines in ~/.zprofile to just one and then reboot your Mac. If it doesn't work after, let me know what echo $PATH says.
—
Reply to this email directly, view it on GitHub <#5259 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM4R6IURHP3MXALGHUH3HHTY3ZISHAVCNFSM6AAAAABFXZDQ42VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TAMJYGIYDE>.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
|
What does |
Beta Was this translation helpful? Give feedback.
-
|
This is a brand new Mac Mini, M2. macOS Sonoma Version 14.4.1I do not know if it matters, but .zprofile.pysave has no "# Setting PATH for Python . . . etc" for Python 3.11 as it does for versions 3.8 & 3.9. nor any thing else reflecting current activity. I thought about taking this to the Apple Support Community, but the first thing that they will do is jump me for having Homebrew on the box. |
Beta Was this translation helpful? Give feedback.
-
|
It needs to have exactly one |
Beta Was this translation helpful? Give feedback.
-
|
Why? given all that I have pointed out in the past? That did not work at all in the past efforts as indicated above. I started out with one in .zprofile and it would last ONE terminal session ONLY. Then I would have to re-enter the two command lines to get things to work again and another eval line would be entered into .zprofile and so on, hence the multiple listings that I showed you. So in my opinion, currently it makes no difference if anything is in there or not. The path variables that I show below works for now with nothing entered into it although I suspect that I can enter the command lines to get it re-entered into .zprofile but it will do nothing for me, seeing as how the exports in .zshrc works. Again, I can ask the Apple Communities (is it a combination of an M2 machine[actually?] and Sonoma?) about this, but the first thing that they will do is jump me about having Homebrew installed and blame all my issues on Homebrew; I have no doubt that someone will even say "Homebrew strikes again!" |
Beta Was this translation helpful? Give feedback.
-
Because a quick search here and in the old support forum reveals that you are the very first person to ever have this issue. Millions of people use Homebrew, and a good chunk of those use M-series processors without this issue.
Maybe the community does, but that's not something Homebrew can help with. Apple has featured Homebrew in their keynotes so clearly it's not the company position. |
Beta Was this translation helpful? Give feedback.
-
|
I have been installing Homebrew for years on various Macs and never had an issue until now. This is a new, clean M2 machine. I have uninstalled and reinstalled Homebrew several times and tried that command line several times and it has not worked except for one terminal session sittings. |
Beta Was this translation helpful? Give feedback.
-
|
Now this is what my path looks like now: |
Beta Was this translation helpful? Give feedback.
-
|
I finally got something to work, but I do not feel that it is a true long term solution. It took two path change edits to .zshrc: export PATH=/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin |
Beta Was this translation helpful? Give feedback.
-
I'd bet you're actually resetting your Run the following command: then post the contents of |
Beta Was this translation helpful? Give feedback.
-
|
I am sorry, however, I dont think so. I had nothing there for a long time and it was not working until I ran the export paths; also, the echo paths command continued to show a very simple path line until I entered the export paths i.e. /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin |
Beta Was this translation helpful? Give feedback.
-
|
@gromgit |
Beta Was this translation helpful? Give feedback.
-
Then I'm sorry too...to have to tell you that your (possibly faulty) recollection means diddly-squat when trying to resolve this particular problem, and that only seeing what's really happening matters. Since you seem to have rejected my suggestion, you have just one option left to get to the bottom of this. It's a rather involved process:
But if you're tired of trying random stuff in the hopes that something will stick, and just want to find out what's happening on your machine that's screwing up your Homebrew config, simply run the command I posted, which actually traces your entire shell startup process (hence the "trace" in the log file name). If you need help figuring it out, post it here like I suggested. TCIY: The Choice Is Yours. |
Beta Was this translation helpful? Give feedback.
-
|
All you needed to say is what it would do with no trail of tears. |
Beta Was this translation helpful? Give feedback.
-
|
Here is something that I forgot about. When I set up this Mac mini, I did not use the new computer option, but used the copy from another Mac, in this case a 2017 intel iMac. So in reality I suppose that it was not really a new CLEAN mini. |
Beta Was this translation helpful? Give feedback.
-
More like walking away from a duct-taped pinhole in a pressure vessel. The underlying problem is still there, but you're assuming it won't affect anything else now and forever. |
Beta Was this translation helpful? Give feedback.
-
|
Nope, it stops automatically at the end of the startup process. Does your normal session startup require you to key in anything? |
Beta Was this translation helpful? Give feedback.
-
|
It appears to stop, however, at every command line, it seems to restart and leave a lot of lines and ends partly ends until I hit return, |
Beta Was this translation helpful? Give feedback.
-
|
I guess that it is printing the log to the screen also |
Beta Was this translation helpful? Give feedback.
-
|
the log is below |
Beta Was this translation helpful? Give feedback.
-
Yes, so that you can see the startup process in action. That bit about "restart and leave a lot of lines", however, suggests that you're actually still in the traced shell session. Type |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hope that I did this right. |
Beta Was this translation helpful? Give feedback.
-
|
Looks OK. In fact, it looks as if you're not setting PATH manually in |
Beta Was this translation helpful? Give feedback.
-
|
And do you now only have one instance of |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I went in with bbedit and changed those files. Actually, I just wiped the internal SSD and reinstalled Sonoma and now the path I suppose is 'normal' to start with: but for some reason I forgot to copy my .zshrc file to my external drive. I can't believe it. However, I have one up in East Texas that I email myself in a week or two. but I guess that it is reinstall Homebrew and see what happens now. Clouded over, so no eclipse for me. |
Beta Was this translation helpful? Give feedback.
-
|
That got it. Homebrew is working. That transfer from that old iMac somehow appears to have gotten Ventura and Sonoma all mixed together. |
Beta Was this translation helpful? Give feedback.
-
Output of
brew configOutput of
brew doctorDescription of issue
I just got a new Mac mini (M2) and Sonoma 14.4.1. I had no issues getting Homebrew to function after installing it on my old iMac and Ventura and previous versions of macOS/osX
If I use the recommended:
echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> /Users/me/.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"
I can get brew commands to work for THAT terminal session only. I just discovered that I can only get things that were installed by Homebrew such as Python3.11 to work during that same terminal session only also.
Therefore, once I exit the terminal and quit it, all things Homebrew are gone when I reopen terminal and I have to go through entering those commands again.
When I have brew working I get no negative reports from brew doctor.
Is there a real fix for this?
Beta Was this translation helpful? Give feedback.
All reactions