-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing on Mojave #249
Comments
the same problem with me |
the same problem with me |
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
Hope it will help. It's a temporary solution. The version is 7.1.19 on my laptop (latest public beta of Mojave). |
Same problem after php 5.6 installing:
|
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. |
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:
BTW: The php binary on the cli works. As does apparently php-fpm, just loading the library in apache has a "permission" problem. |
Unfortunatley similar problem here after installing php7.3 and php7.2
|
Problem solved for me, first of all run |
php liip works fine with apache installed from homebrew (brew install https) Quick steps:
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 |
Slightly different error on Mojave when trying to access earlier install and use of php5
I really don't want to switch to using homebrew at this time |
Works fine with homebrew installed apache Steps to make it work:
|
Confirming that @Gulivertx and @suneet64 solutions are correct. I've tested it now with PHP 7.2.9 package. |
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) |
@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. |
This doesn't help installing, but if you need to get PHP working locally the following worked for me based on https://tobschall.de/2018/08/08/mojave-mamp/ which states that Mojave ships with PHP 7.1.x. I edited "/etc/apache2/httpd.conf" and added "LoadModule php7_module libexec/apache2/libphp7.so" below all the other LoadModule calls located at the top of the conf file. Then I added the path to my alias below "" and restarted apache. All good so far! |
Work for me: After that, run |
In this case, in which folder are Apache installed ? On 'etc/apache2' ? |
/usr/local/ It’s call httpd |
Where is the correct httpd.conf after install Apache with 'brew install httpd' ? |
So i could follow the installations steps but now when i go to 127.0.0.1/myapp, the browser shows the php code instead of executing it... any hints ? |
I think switching to another apache installation is not a suitable solution for everyone... Did someone actually got brew php to work with built-in apache? |
I think brew php would have the same issue with the permission/security features of the apple provided apache. |
Apple is aware of this issue, I just got my radar duped. |
Oh, good to hear. Hope there will a solution to this |
So for now the only suitable solution is to reinstall apache via brew? |
If you can't live with the php module provided by apple, yes, that's the only solution I know of |
Well... I have some projects that only works on php5.6 so php7 won't work... Unfortunately for me I cannot wait for a solution from Apple :/ |
I also encounter the problem. As suggested, I reactivated the PHP 7 extension provided with Mojave. I still have a problem. How to enable intl.so extension with this PHP Mojave version ? thank you, |
tho re-enable the built in apache to work with unsigned files one could also disable "SIP"
apple will consider this a security-issue. if you know what you are doing - it's not. |
I feel this is the quickest way to make things work again for me. Thank you! @martinsnajdr Just wanna mention the file is located at |
Just a note: installing Apache through Homebrew may change the
It also need to be fully configured to support PHP, requires to reconfigure the document root and all other customizations you may have made to your built-in Apache. |
Thanks! I followed your instructions, yet instead of step 6, I installed php56 using brew. However I got the following error in my apache logs: AH00052: child pid 4540 exit signal Segmentation fault (11). I found here that it helps to comment out all lines in /usr/local/etc/php/5.6/conf.d/ext-opcache.ini. It worked for me. It might also help someone else. |
Same problem here. Segfaults remain... any further clues? |
Any solution to sign new extensions? The built-in package works well but can't get intl to work with it. Any idea? |
Appeared here after googling the error. Got it after trying to launch Apache with PHP 5.6 installed by Homebrew. So I haven't used this tool, I mean just to be clear the issue with PHP package itself. |
This should be fixed in 10.14.4 |
Is fixed in Mojava 10.14.4. |
@roydukkey unfortunately issues in Apple's Radar aren't public, so no there's nothing I can point at. However I can tell you that Apple marked my issue as fixed for 10.14.4 and that in my testing all of my boxes running 10.14.4 can once again load 3rd party modules into Apple's Apache. |
Before I set to try installing PHP 7 using homebrew, can someone reconfirm, is it really fixed on the latest version of Mojave 10.14.4 ? |
I have the Apache / php library signing warning happening... wont load |
Ok, I have installed 10.14.4 |
So to be more specific
*** Dont forget to save changes *** My PHP5 installation is part of the entropy.ch PHP package for Mac OS X In my /private/etc/apache2/other/ folder I have a file like +php5-osx.conf that is a symlink to /usr/local/php5-5.6.31-20170817-164511/entropy-php.conf
So this got my PHP 5 working again on Mojave |
I have figured it out on Mojave 10.14.4 What I've done to use 7.2.9 is to download it using the instructions on https://php-osx.liip.ch/ and then directly calling the module in
Saving and then restarting I've written about it also on my blog: https://www.ibenic.com/installing-php-mojave/ |
@igorbenic - seem to work for me with PHP 7.3. So far, anyway :) |
Hi, Mac OS X 10.14 and php 7.1.19 Need to upgrade to 7.2 to get a cms working on localhost. Followed steps from @suneet64 but ended up with the same warning:
[WARNING] Restart this script with ➜ / Any suggestions on how to proceed to get to 7.2? Thanks in advance! |
How to remove php installed by your script? |
|
@treken1 Your suggestion didn't work for me on Mojave 10.14.5. I still get the same error as before.
|
https://php-osx.liip.ch/#uninstall Does that not work? |
@chregu Not sure, but installing php using brew ( |
This project is now deprecated and won't get any more updates (since quite some time, but we made it official now). The binaries and scripts will still be available for the foreseeable future. We recommend using a homebrew based setup for an up-to-date local and native PHP experience. See https://php-osx.liip.ch/ for more details. |
Hello.
This is what I get:
after installing 7.2 on Mojave.
Ideas?
The text was updated successfully, but these errors were encountered: