I was having trouble getting MAMP (MAMP PRO, actually) to work with Drush after I restored my environment from a backup after a hard drive failure. MAMP was working fine in the browser, but drush was giving the classic non-functional environment error. I found #1226422: mamp 2.0 drush cant fint mysql.sock which led me to discovering this issue.

README.txt (lines 85-87):

If you want to use php 5.3.x, add this line instead

export PATH="/Applications/MAMP/Library/bin:/Applications/MAMP/bin/php5.3/bin:$PATH"

I amended the path above to:

export PATH="/Applications/MAMP/Library/bin:/Applications/MAMP/bin/php/php5.3.6/bin:$PATH"

...and drush started working.

I'd have rolled a patch here, but I believe this path is likely to change in any minor MAMP update that changes to a different point release of php 5.3.x. Not sure what the fix would be here, aside from some general mention of finding MAMP's paths and making sure they are included in the bash profile.

Comments

greg.1.anderson’s picture

Category: bug » task

Perhaps the docs should suggest that something like find /Applications/MAMP/bin -name "bin" could be used to find the right php bin directory.

greg.1.anderson’s picture

Version: » 8.x-6.x-dev
Status: Active » Closed (won't fix)
Issue tags: +Needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If desired, you may copy this task to our Github project and then post a link here to the new issue. Please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.