-
Notifications
You must be signed in to change notification settings - Fork 53
PHP 5.6 and 7.0 doesn't run on Catalina - openssl 1.0.0 needed #14
Comments
I had the same error since I've update & upgrade brew. (to install php7.4) |
Ok I fix it, you need to install the old version of openssl, but it doesn't exist anymore on homebrew. |
Yes, it looks like Brew deprecated openssl v1.0 in favour of v1.1.
And that installs openssl 1.0 and fixed my issue. |
Hi! Thanks for reporting the issue. We got the same issue while provisioning a new laptop. And we still have not figure out how to fix it. The solution proposed by @leanormandon works, because it is using the existing bottle from Homebrew. But if I try to rebuild the bottles (for Without a successful build of Regards. EDIT: I said |
I tried removing openssl v1.1 and installing the openssl v1.0 that @leanormandon linked but still run into issues:
Edit:
|
Hi @eoswald , thanks for your answer, this is a life-saver. After following your steps I'm still having trouble starting apache, though:
Any clue about how to fix this? Thanks again. EDIT: solved with these two
|
I put the old openssl in my tap to save you some time.
afterwards
|
Thanks all for solving this. A combination of the last two answers worked for me:
|
This doesnt work for me. I still get this message when get to the point of running: "$ brew reinstall php@5.6" :
Anyone that run into the same issue? I have been struggling for quiet a while. It all started when I upgraded brew. Next this, my apache and php5.6 stop working. I need this specific version of php in the project Im working in. Btw, Im on MAC OS Sierra High |
@amichia My instructions work for me on Catalina, sorry no possibility to test High Sierra. |
Hi @tholu! No worries, I could finally solve it without brew, just installing php5.6 in one line command following this guide: |
https://www.sminrana.com/php/install-php-5-6-on-macos-catalina/ Helped me - now it works. |
@eoswald saved me a lot of time. Thanks |
I am still not able to get this working properly in High Sierra. I've had a few problems trying the suggestion in @jonom #14 (comment), the major ones seem to be:
Gave up for the time being, but I think I could get it working if I hacked the |
After this procedure, this message appears dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.64.dylib MacOS Catalina |
For eveyone interested. php@7.0 does not require openssl 1.0.0 it can be recompiled to use 1.1
php@5.6 can be patched to compile against openssl 1.1.x. |
@JParkinson1991 Thanks for the update on this. I have come across a possible bug / issue, which I have isolated to Using a completely fresh install of OS X Catalina on
These all subsequently install additional packages (attached) This is the third test doing the same thing, where by I install a fresh copy of OSX Catalina and install the brew packages, each time I have install Each PHP services has been stopped prior to testing the next version with the conclusion: I understand it's possible to update the limits on OSX as they are "apparently" quite low, but from my stance this seems to be masking an issue when PHP 7.3/7.4 work with no issues. I am guessing it's something within EDIT I thought I would raise this a possible problem. Please let me know your thoughts on this one. Thanks in advance. |
@boxxroom Given you're importing the database via Sequel Pro i dont think this has anything to do with PHP, nor do i think PHP, the version of it or the fact it was built from source is the cause of this problem. My guess is this is a problem local to the database installation itself, in your case MariaDB. You probably need to look at configuring |
Thanks for you reply @JParkinson1991. As mentioned previously, the issue of import, exporting, deleting of tables, databases or SQL statements does not have any issues on PHP7.3/PHP7.4. I might also add (which I had forgotten) this is when PHP7.0 hasn't been installed otherwise using PHP7.+ has the same effect. Sequel Pro or Terminal it doesn't matter the issue / error output is still the same. Why would this error only occur with the installation of PHP7.0? Again, like I mentioned I understand you can increase the limits of OS X but this seems like masking the issue, why would the error not occur on PHP7.3/PHP7.4 (without PHP7.0 installed). I am curious. I would like to say, either way - I really appreciate and respect you taking the time to patch PHP7.0 to work on new OSX version. |
Amazing, sort & sweet solution, spent two days for this solution. |
I maintain a homebrew tap with PHP 5.6 to a nightly build of PHP 8.1. PHP 5.6 and PHP 7.0 have been rebuilt to use |
@shivammathur ++++++++ Thank you for all that! I've been struggling to find an easy way to document for other developers I work with to get the correct (but old...5.6...yuck) version of PHP installed. |
I forked @tholu 's tap and add $ brew tap cloudycity/tap
$ brew install icu4c@64.2
$ sudo ln -s /usr/local/opt/icu4c@64.2/lib/libicudata.64.dylib /usr/local/opt/icu4c/lib/libicudata.64.dylib
$ sudo ln -s /usr/local/opt/icu4c@64.2/lib/libicui18n.64.dylib /usr/local/opt/icu4c/lib/libicui18n.64.dylib
$ sudo ln -s /usr/local/opt/icu4c@64.2/lib/libicuuc.64.dylib /usr/local/opt/icu4c/lib/libicuuc.64.dylib
$ sudo ln -s /usr/local/opt/icu4c@64.2/lib/libicuio.64.dylib /usr/local/opt/icu4c/lib/libicuio.64.dylib But i think @shivammathur 's resolution is the best. Updated |
@CloudyCity If you provide a pull request, I'll happily accept it in my tap. However, I also think that @shivammathur is the best right now - thanks a lot! |
Hi! Thank you for your interest in this repository. Unfortunately, this repository will now be archived with no further actions. We are sorry for the inconvenience. Why are we closing this repository? This repository was only meant as a temporary measure, not a permanent one. Its only purpose was to ease the transition, considering that formulae from the homebrew-core tap are removed almost the day they became unsupported by the vendor. We needed a few more months to allow us to upgrade the code base of the various projects we have. But it was always with the intention of doing those upgrades, not by relying on a repository to keep old php versions artificially alive. We do not condone the use of deprecated software that could lead to serious security vulnerabilities. Why are we not redirecting to another repository? Redirecting to another repository could be interpreted as an endorsement of said repository. If we were to do such a thing, we would not do it without vetting it first. And we do not wish to put the time and energy required in a vetting process of a third party repository. As the reason why a vetting process would be required, consider this. Before installing a software library on all our developer computers from an untrusted source, we would need to make sure that this software library is free from any malicious code (Trojan, ransomware, etc.), both in the repository itself and in the packaged binaries (the homebrew bottles, if any). Thank you for your understanding. |
Install fails, and running php-v returns
on a brand new Catalina MacBook.
I'm unsure if this is an error here, or elsewhere.
The text was updated successfully, but these errors were encountered: