Dev Stack Source

Answer : I had the similar problem but with another package. Turned out there had been a bunch of dead links pointing to the old version all other my file system. Here is what helped in my case: Run brew link <appname> (e.g. brew link postgress ); If completed successfully then you are golden, otherwise proceed with the next step; Take a look at the path in the error message (e.g. /usr/local/Cellar/postgresql/9.2.3/include/server ) transform the path by removing the Cellar/<app name>/<version> from it (e.g. /usr/local/include/server ) Find under that path all links referring to Cellar/<app name>/<version> and remove them; Goto step 1. Hope that helps brew update brew doctor is always first steps. to help finding files, update the files db sudo /usr/libexec/locate.updatedb this is similar to updatedb on ubuntu and you might want to alias it. then you may perform locate postgresql and learn more about where things are. Chanc...

Answer : This fixed it for me cd `brew --prefix`/Homebrew git fetch origin git reset --hard origin/master brew update worked fine after that Solution You might still find.. brew update not working after git pull origin master Here what you need to do. cd /usr/local git pull origin master brew install git Now you might already have git on your System, but what this will do it that now. Your broken brew update will automatically be updated before at first run.. Here is the link to the origin issue in HomeBrew. brew stuck I simply removed the .git directory inside of the /usr/local directory, then ran the command brew update .

Answer : There are two steps to installing nvm with brew. First use brew to install the application: brew install nvm Then take a look at the brew info "caveats" section, to see what else you have to do: brew info nvm You might see something like (this can change!): You should create NVM's working directory if it doesn't exist: mkdir ~/.nvm Add the following to ~/.bash_profile or your desired shell configuration file: export NVM_DIR="$HOME/.nvm" . "/usr/local/opt/nvm/nvm.sh" If you do not have a ~/.bash_profile file, then you can simply create one. Make sure to restart your terminal before trying the command. From the docs: Your system may not have a [.bash_profile file] where the command is set up. Simply create one with touch ~/.bash_profile and run the install script again you might need to restart your terminal instance. Try opening a new tab/window in your terminal and retry. Restarting worked f...

Answer : Add this repository: https://github.com/josegonzalez/homebrew-php#readme Then use brew install php54-xdebug for PHP 5.4 Or brew install php53-xdebug for PHP 5.3 Or brew install php55-xdebug for PHP 5.5 // Working as of 2021 As homebrew removed the extra php repository containing a version with xdebug already installed, you have to install it manually. Summary: brew install <php version> for php update your path pecl install xdebug for xdebug Full example: # update homebrew brew update # install a version of php, e.g. 7.0 brew install php@7.0 # now they tell you how to link it, in my case echo 'export PATH="/usr/local/opt/php@7.0/bin:$PATH"' >> ~/.bash_profile echo 'export PATH="/usr/local/opt/php@7.0/sbin:$PATH"' >> ~/.bash_profile # reload the file with the updated path, so we can use pecl source ~/.bash_profile # check that the path is to the correct php executable, # and pecl is available whi...

Answer : Just run in the command line: xcode-select --install In OS X 10.9+, the command line developer tools are now installed on demand. So after running this also zlib and zlib-devel should be available (no need for brew install zlib...) For OS X Mojave sudo installer -pkg /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg -target / The reason is because Xcode Command Line tools no longer installs needed headers in /include. You have to run a separate command to install the needed headers. As noted here - https://developer.apple.com/documentation/xcode_release_notes/xcode_10_release_notes The command line tools will search the SDK for system headers by default. However, some software may fail to build correctly against the SDK and require macOS headers to be installed in the base system under /usr/include. If you are the maintainer of such software, we encourage you to update your project to work with the SDK or file a bug...

Answer : I think one can end up in this position with older versions of mysql already installed. I had the same problem and none of the above solutions worked for me. I fixed it thus: Used brew's remove & cleanup commands, unloaded the launchctl script, then deleted the mysql directory in /usr/local/var , deleted my existing /etc/my.cnf (leave that one up to you, should it apply) and launchctl plist Updated the string for the plist. Note also your alternate security script directory will be based on which version of MySQL you are installing. Step-by-step: brew remove mysql brew cleanup launchctl unload -w ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist rm ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist sudo rm -rf /usr/local/var/mysql I then started from scratch: installed mysql with brew install mysql ran the commands brew suggested: (see note: below) unset TMPDIR mysql_install_db --verbose --user=`whoami` --basedir="$(brew --prefix mysql)...