Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103596
MIME-Version: 1.0
References: <c092bd28-f212-5ee2-36e7-368724480da3@evermeet.cx>
 <e93bb835-5489-01ef-b29d-189d48276af0@evermeet.cx> <CAEKnhAEgC1G-z9LjzdBCEThmEDpw0FU3Y=ErpSoPtkOpHnqg8g@mail.gmail.com>
 <2e358c47-f07d-2bd0-dcbf-8ee1282f1ea1@evermeet.cx>
In-Reply-To: <2e358c47-f07d-2bd0-dcbf-8ee1282f1ea1@evermeet.cx>
Date: Wed, 12 Dec 2018 15:37:49 +0000
Message-ID: <CAEKnhAFN1TNsOSuOVC0gszL=4eBWfePq9XxqJweEwTnchwKOtw@mail.gmail.com>
To: tessarek@evermeet.cx
Cc: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a3abc2057cd4fbf5"
Subject: Re: [PHP-DEV] configure bug with static openssl 1.1.1?
From: bukka@php.net (Jakub Zelenka)

--000000000000a3abc2057cd4fbf5
Content-Type: text/plain; charset="UTF-8"

On Wed, Dec 12, 2018 at 3:32 PM Helmut K. C. Tessarek <tessarek@evermeet.cx>
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

--000000000000a3abc2057cd4fbf5--