MacOS – PHP MAMP user not finding /usr/local/bin

apachemacosmampPHP

I have a website in a shared Linux hosting that uses Ghostscript. I use by php exec function that executes command line functions, gs commands to render PDF files, by simple gs commands.

gs -h (will display info)

However, in my Mac OS X MAMP web server gs commands are only executed by full paths.

/usr/local/bin/gs -h (will display info)

How do I configure my local system so "php" user will find gs (and other libraries) without full path?

EDIT: Command line by Terminal does not need full path either. The problem is only when trying to execute gs by exec PHP function.

Best Answer

This is most likely an issue with the default search path on MacOS X not including that directory. Homebrew is affected by that as well, so they list a workaround on their FAQ page:

launchctl setenv PATH "/usr/local/bin:$PATH"

That FAQ entry also helpfully references https://stackoverflow.com/questions/135688/setting-environment-variables-in-os-x/5444960 for more details about setting environment in OS X.

Related Solutions

How to increase command line memory_limit for PHP with MAMP PRO

Instead of guessing which php.ini you need to alter, run this command to locate the file:

php -r 'phpinfo();' | grep 'php.ini'

Even though I use MAMP PRO, by default my command-line PHP commands are not executed using their copy of PHP. In my case it says the file is found at /etc/php.ini

Once you have located the file, follow the instructions on all of the other answers to bump the memory_limit setting:

memory_limit = 256M

MacOS – Why “which” command does not give you the correct path

which is an external program, which tries to determine how your shell will resolve a command from the existing $PATH, but it is possible for it to get it wrong.

If you're using bash as your shell, use the bash built-in command "type" to have the shell itself tell you how it will resolve that command:

$ which mvn
/usr/bin/mvn
$ type mvn
mvn is /usr/bin/mvn
$ type type
type is a shell builtin
$ type which
which is hashed (/usr/bin/which)

You can see here that in my environment that /usr/bin/which and the shell built-in type agree. In yours it seems they don't, though I am curious why they don't. Perhaps you have PATH changes that were not exported? Try "export PATH" and then "which mvn" again.

Best Answer

Related Solutions

How to increase command line memory_limit for PHP with MAMP PRO

MacOS – Why “which” command does not give you the correct path

Related Question