Skip to content
This repository has been archived by the owner on Oct 20, 2021. It is now read-only.

PHP5.6 build not working on High Sierra #17

Closed
theredled opened this issue Jan 27, 2020 · 3 comments
Closed

PHP5.6 build not working on High Sierra #17

theredled opened this issue Jan 27, 2020 · 3 comments

Comments

@theredled
Copy link

I have that Make error:

==> ./buildconf --force
==> ./configure --prefix=/usr/local/Cellar/php@5.6/5.6.40 --localstatedir=/usr/local/var --sysconfdir=/usr/local/etc/php/5.6 --with-config-file-path=/usr/local/etc/php/5.6 --with-config-file-scan-dir=/usr/local
==> make
Last 15 lines from /Volumes/Macintosh HD Data/Users/theredled/Library/Logs/Homebrew/php@5.6/03.make:
typedef struct rsa_st RSA;
               ^
/private/tmp/php@5.6-20200127-2001-9rc1fa/php-5.6.40/ext/openssl/openssl.c:3619:6: error: incomplete definition of type 'struct rsa_st'
                                        OPENSSL_PKEY_SET_BN(Z_ARRVAL_PP(data), rsa, d);
                                        ^                                      ~~~
/private/tmp/php@5.6-20200127-2001-9rc1fa/php-5.6.40/ext/openssl/openssl.c:3548:9: note: expanded from macro 'OPENSSL_PKEY_SET_BN'
                        _type->_name = BN_bin2bn(                                                                       \
                        ~~~~~^
/usr/local/opt/openssl@1.1/include/openssl/ossl_typ.h:110:16: note: forward declaration of 'struct rsa_st'
typedef struct rsa_st RSA;
               ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.

Any idea?

@theredled theredled changed the title Build not working on High Sierra PHP5.6 build not working on High Sierra Jan 27, 2020
@theredled
Copy link
Author

theredled commented Jan 27, 2020

Seems related to #14
But not the same as the message is different and PHP 7.0 builds well for me.

@kharizma
Copy link

kharizma commented Feb 8, 2020

same here

`
Last 15 lines from /Users/kharismaputra/Library/Logs/Homebrew/php@5.6/03.make:
typedef struct rsa_st RSA;
^
/private/tmp/php@5.6-20200209-40081-16ueh17/php-5.6.40/ext/openssl/openssl.c:3619:6: error: incomplete definition of type 'struct rsa_st'
OPENSSL_PKEY_SET_BN(Z_ARRVAL_PP(data), rsa, d);
^ ~~~
/private/tmp/php@5.6-20200209-40081-16ueh17/php-5.6.40/ext/openssl/openssl.c:3548:9: note: expanded from macro 'OPENSSL_PKEY_SET_BN'
_type->_name = BN_bin2bn(
~~~~~^
/usr/local/opt/openssl@1.1/include/openssl/ossl_typ.h:110:16: note: forward declaration of 'struct rsa_st'
typedef struct rsa_st RSA;
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make: *** [ext/openssl/openssl.lo] Error 1
make: *** Waiting for unfinished jobs....

If reporting this issue please do so at (not Homebrew/brew or Homebrew/core):
https://github.com/exolnet/homebrew-deprecated/issues

These open issues may also help:
PHP 5.6 and 7.0 doesn't run on Catalina - openssl 1.0.0 needed #14
`

@pgrenaud
Copy link
Contributor

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants