Am 11.10.19 um 15:16 schrieb Claude Pache:
Le 11 oct. 2019 à 13:05, Nikita Popov a écrit :
I'm mainly wondering how exactly we'd go about integrating this in the
existing exception hierarchy. Assuming that it is desirable to allow people
to actually catch this exception, my first thought woul
"Helmut K. C. Tessarek" in php.internals (Thu, 7 Feb 2019 13:39:11
+0100):
>On 2018-12-13 17:52, Rainer Jung wrote:
>> I might be wrong, but I vaguely remember that PHp does not call
>> "pkg-config --static --libs openssl" with a correctly setup
>> PKG_CONFIG_PAATZ to get the libs needed for static
On 2019-10-13 16:50, Jan Ehrhardt wrote:
> Did you ever find a solution to compile PHP with a static OpenSSL 1.1.1?
Unfortunately not. I really hoped that someone would look into it, but I guess
security is not that important.
--
regards Helmut K. C. Tessarek KeyID 0x172380A011EF494
On Sun, Oct 13, 2019 at 10:51 PM Jan Ehrhardt wrote:
> "Helmut K. C. Tessarek" in php.internals (Thu, 7 Feb 2019 13:39:11
> +0100):
> >On 2018-12-13 17:52, Rainer Jung wrote:
> >> I might be wrong, but I vaguely remember that PHp does not call
> >> "pkg-config --static --libs openssl" with a corr
On 2019-10-13 17:00, Nikita Popov wrote:
> Don't know about previous versions, but at least on 7.4 setting
> OPENSSL_CFLAGS and OPENSSL_LIBS appropriately (e.g. using pkg-config
> --static --cflags/--libs return values) should work. These environment
> variables allow you to bypass normal pkg-confi
