bash_profile should be adjusted like this: export MAMP_BIN=/Applications/MAMP/Library/binĮxport MAMP_PHP=/Applications/MAMP/bin/php/php5.5.14/binĮxport PATH="$MAMP_BIN:$MAMP_PHP:$PATH:/Users//bin"Īlso, that /Users//bin seems kludgy and too specific for me. Traditionally this would be in the /Applications/MAMP/Library/bin/ directory along with other MAMP core binaries. profile-which is a nice way of logically separating paths for human eyes-and how I simply set that value to /Applications/MAMP/bin/php/php5.5.14/bin since I have no idea when this MySQL path would be used: /Applications/MAMP/bin/mysql.įrom my vantage point using MAMP version 2.1.3 I don’t see an actual mysql binary in the path you have set. Note how I am using the $MAMP_PHP convention from.
bash_profile like this to make it work: export MAMP_PHP=/Applications/MAMP/bin/php/php5.5.14/binĮxport PATH="$MAMP_PHP:$PATH:/Users//bin" bash_profile version you are appending this stuff after $PATH: :/Applications/MAMP/bin/php/php5.5.14/bin:/Applications/MAMP/bin/mysql profile version you are setting $MAMP_PHP as a variable and then prepending it to the beginning of the $PATH. Knowing that you can breakdown the behavior you are seeing like this: The key to solving this is to look at where you are setting your new MAMP related items when compared to the default $PATH order counts because the shell will act on (key thing) the first item it finds in its list of user search paths.
profile: export MAMP_PHP=/Applications/MAMP/bin/php/php5.5.14/bin bash_profile: export PATH="$PATH:/Users//bin:/Applications/MAMP/bin/php/php5.5.14/bin:/Applications/MAMP/bin/mysql"Īnd here is your. bash_profile (which doesn’t work) when compared to. I believe the answer is clear when you look at the logical order of what you have set in.
0 kommentar(er)
