Installing on Mojave

[phaistonian]

Hello.

This is what I get:

❯ sudo apachectl configtest
httpd: Syntax error on line 545 of /private/etc/apache2/httpd.conf: Syntax error on line 8 of /private/etc/apache2/other/+php-osx.conf: Cannot load /usr/local/php5/libphp7.so into server: dlopen(/usr/local/php5/libphp7.so, 10): no suitable image found.  Did find:\n\t/usr/local/php5/libphp7.so: code signing blocked mmap() of '/usr/local/php5/libphp7.so'\n\t/usr/local/php5/libphp7.so: stat() failed with errno=22

after installing 7.2 on Mojave.

Ideas?

[maxisoft-git]

the same problem with me

[moosti]

the same problem with me

[martinsnajdr]

I had the same problem and the only solution was to use the build in PHP library (shipped with macOS). So I changed the path to load php7_module to the default

LoadModule php7_module libexec/apache2/libphp7.so

Hope it will help. It's a temporary solution. The version is 7.1.19 on my laptop (latest public beta of Mojave).

[Vitassam]

Same problem after php 5.6 installing:

httpd: Syntax error on line 178 of /private/etc/apache2/httpd.conf: Cannot load /usr/local/php5/libphp5.so into server: dlopen(/usr/local/php5/libphp5.so, 10): no suitable image found. Did find:\n\t/usr/local/php5/libphp5.so: code signature in (/usr/local/php5/libphp5.so) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.\n\t/usr/local/php5/libphp5.so: stat() failed with errno=22

[martinsnajdr]

Well, I have similar problems with some php packages (like APCu). There is not much information about it, but I read somewhere that Mojave is somehow more strict about app / script / package signatures. I think that the only thing we can do is to wait... Mojave (not beta) was released yesterday, so I hope the devs are gonna fix this soon.

[chregu]

Grr, yes. Does not work in apache right now. No idea how to sign that stuff correctly. Some basic experiments failed, they also showed, that you can't load "foreign" libraries into system process (like httpd). Not sure, if there's a workaround/solution for that. I hope so.

Alternatives right now:

• Use the apple provided php library (It's php 7.2 after all).
• Switch to php-fpm, the binary is in /usr/local/php5/sbin/php-fpm - Not much is provided regarding how to set that up, but maybe someone can figure it out and post it here. (If you use some .htaccess apache magic, switching to php-fpm will be more work than maybe expected)
• Try setting up httpd and php with homebrew: https://gist.github.com/DragonBe/0faebe58deced34744953e3bf6afbec7 (didn't test)

BTW: The php binary on the cli works. As does apparently php-fpm, just loading the library in apache has a "permission" problem.

[Endeauvirr]

Unfortunatley similar problem here after installing php7.3 and php7.2

httpd: Syntax error on line 177 of /private/etc/apache2/httpd.conf: Cannot load /usr/local/php5/libphp7.so into server: dlopen(/usr/local/php5/libphp7.so, 10): no suitable image found. Did find:\n\t/usr/local/php5/libphp7.so: code signature in (/usr/local/php5/libphp7.so) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.\n\t/usr/local/php5/libphp7.so: stat() failed with errno=22

[moosti]

Problem solved for me, first of all run brew update & brew upgrade then follow steps in this link (It is 3 part)

[Gulivertx]

php liip works fine with apache installed from homebrew (brew install https)

Quick steps:

• sudo apachectl stop <- stop default Apache2 from Apple
• sudo launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist <- remove default Apache from launchd (autostart)
• brew install httpd <- install apache2 from homebrew
• sudo brew services start httpd

Default port for Apache from brew is 8080 you should change it in the config files, also add at the end of the conf file Include /private/etc/apache2/other/*.conf
the config is located in /usr/local/etc/httpd/httpd.conf

[1fifoto]

Slightly different error on Mojave when trying to access earlier install and use of php5

httpd: Syntax error on line 545 of /private/etc/apache2/httpd.conf: Syntax error on line 8 of /private/etc/apache2/other/+php-osx.conf: Cannot load /usr/local/php5/libphp5.so into server: dlopen(/usr/local/php5/libphp5.so, 10): no suitable image found.  Did find:\n\t/usr/local/php5/libphp5.so: code signature in (/usr/local/php5/libphp5.so) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.\n\t/usr/local/php5/libphp5.so: stat() failed with errno=22

I really don't want to switch to using homebrew at this time

[suneet64]

Works fine with homebrew installed apache

Steps to make it work:

1. macOS comes with pre-installed apache, following are the commands to stop it and prevent from autostart on boot:
   $ sudo apachectl stop
$ sudo launchctl unload /System/Library/LaunchDaemons/org.apache.httpd.plist 2>/dev/null

2. Install apache through homebrew
   $ brew install httpd

3. Check apache installation through the following command and the output should be /usr/local/bin/apachectl
   $ which apachectl

4. Start apache through the following command
   $ sudo apachectl -k start

5. Set apache to startup on bootload
   $ sudo brew services start httpd

6. Re-install php from https://php-osx.liip.ch link.

[Endeauvirr]

Confirming that @Gulivertx and @suneet64 solutions are correct. I've tested it now with PHP 7.2.9 package.
Homebrew apache have no problems with this - so its currently the best option I think until resolving this issue.

[chregu]

I still didn't come up with any solution with using the built-in apache. Maybe the homebrew aproach is the best one. One could also switch totally to homebrew, also for the PHP part. The tutorial over at https://getgrav.org/blog/macos-mojave-apache-multiple-php-versions worked for me at least. It's not a liner apparently ;)

Just to decide about the future of this project, what keeps people using this php binary instead of the one by homebrew? If you have compelling reasons, I will think about some more time consuming (for me/us) solutions to keep it going. But from a quick glance, the homebrew solution (with php from there) seems to be good, too.

(the one-liner installation is of course very useful, the homebrew installation needs quite some working in the config files to get it running)

[lowbatteries]

@chregu thanks for you work on this. I for one, prompted by Mojave, have moved to homebrew for my entire stack. I used the same tutorial as you. Since I’m giving up on the built-in Apache, I won’t be needing this package.