Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103605 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 13245 invoked from network); 13 Dec 2018 20:25:01 -0000 Received: from unknown (HELO mailserver.kippdata.de) (212.79.170.253) by pb1.pair.com with SMTP; 13 Dec 2018 20:25:01 -0000 Received: from [10.0.110.6] ([192.168.2.104]) by mailserver.kippdata.de (8.13.5/8.13.5) with ESMTP id wBDGqZFW002485; Thu, 13 Dec 2018 17:52:35 +0100 (CET) To: Jakub Zelenka , tessarek@evermeet.cx Cc: PHP internals list References: <2e358c47-f07d-2bd0-dcbf-8ee1282f1ea1@evermeet.cx> Message-ID: <79bdc208-876f-ea0c-b529-010fe3d129bb@kippdata.de> Date: Thu, 13 Dec 2018 17:52:33 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] configure bug with static openssl 1.1.1? From: rainer.jung@kippdata.de (Rainer Jung) Am 12.12.2018 um 16:37 schrieb Jakub Zelenka: > On Wed, Dec 12, 2018 at 3:32 PM Helmut K. C. Tessarek > wrote: > >> On 2018-12-12 16:11, Jakub Zelenka wrote: >>> >>> You should create a bug report. >>> >>> Please note that a static configuration has some issues (e.g. >>> https://bugs.php.net/bug.php?id=73609 and think there were more issues >>> maybe). Basically it's not well supported so I would recommend to do a >>> shared build instead otherwise you are probably on your own unless >>> someone finds time to look into it. >> >> Thanks, Jakub for your reply. >> >> Hmm, I checked the link you sent, but this ticket has nothing to do with >> linking against a static openssl library. >> >> This ticket mentions that openssl is not supported as a shared >> extension. But that is not what I'm doing. >> >> I try to link against a static openssl library. But it works when >> linking against a static openssl 1.0.2 lib. >> Therefore I highly suspect that there's a problem with configure. But I >> will open a ticket, and I will also try to link against a dynamic >> openssl 1.1.1. >> >> So linking against a static openssl 1.0.2 works, but against a static >> openssl 1.1.1 does not work. >> >> However, linking against a static openssl library should be supported. >> Years back people even suggested to always link against a static openssl >> lib because of security reasons (no hijacking of dynamic libs and >> whatnot). This might not be relevant anymore, but there's no logical >> reason why linking against a static openssl 1.1.1 should not work. >> >> > Ah I see! Yeah I think it should work so it might be a bug if it doesn't. I > would suggest to create a bug report. > > Cheers > > Jakub 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 compilation. Typically OpenSSL installs correct pc files that contain pthread as such a dependency. Without asking pkg-config some fixed decisin logic would need to find all the needed libs. Regards, Rainer