
I did get brew doctor to return with no errors.

Also deleted the bash profile, as the working computer doesn't return one, and.still the same error, so I conclude that "curl is not in path" should be ignored. Still same error so I removed /usr/bin/curl from /etc/paths, and export file. Which curl finally returns the correct path, /usr/bin/curl Rm -rf /opt/local/bin/curl rm -rf /usr/local/bin/curl Still getting a 403 SNI Error cannot download Python 3.9 Start the PostgreSQL again brew services start postgresql After the above, you can also check the status of the service by brew services info postgresql. I'm still getting the error, so I used vim, to sudo edit the /etc/paths file by using However, I forgot I have an identical computer that is working just fine, but when I run "which curl", in the working computer, I get /usr/bin/curl, instead of /usr/local/bin/curl, so I ranĮxport PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/bin/curl" I've also tried to add curl as an alias of curl into the bash profile and it recognized the error after I used this program instead of program, then I installed macports(opened a new terminal window), and installed hwloc with macports, to no avail, just getting totally different errors.
BREW NOT FOUND MAC MAC OS X
Regardless I found a way to install it using Ubuntu commands.īut ran into an issue where I had to download cmake from the developer website and add it to the path in it's menu options on Mac OS X 10.11 to compile and run my program as.

In the case at hand, running type envsubst on macOS 10. After installing docker using Homebrew, start the Docker daemon by searching for Docker in the Application folder in Finder and running it. To test whether a given command is a builtin, use. The main website requires you to install wget, maybe it gets deleted when you uninstall homebrew. Commands directly built into bash are called builtins, and only they can be relied upon to be present on all platforms. I thought I broke my curl symlink somehow too, and somewhere in there I ran into your same issue, where no command would work.
