Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92908
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.51 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
In-Reply-To: <7DD8AF5A-EB68-4CC3-A2E7-E668E30A0F59@heroku.com>
Date: Fri, 29 Apr 2016 01:25:43 +0200
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <E11A8E53-1CE6-435C-B9EA-AB750DBD6ED2@heroku.com>
References: <7D13E7EB-910D-42DD-ACF1-3872C1CE55C1@heroku.com> <3F.65.03587.65DEED65@pb1.pair.com> <0E11F160-CC0B-4161-AA35-9B7863A928D8@heroku.com> <7DD8AF5A-EB68-4CC3-A2E7-E668E30A0F59@heroku.com>
To: Andrea Faulds <ajf@ajf.me>
Subject: Re: [PHP-DEV] Enabling opcache causes libraries to build as static
From: dz@heroku.com (David Zuelke)

On 20.03.2016, at 22:10, David Zuelke <dz@heroku.com> wrote:
>=20
> On 10.03.2016, at 16:56, David Zuelke <dz@heroku.com> wrote:
>>=20
>>> On 08.03.2016, at 16:18, Andrea Faulds <ajf@ajf.me> wrote:
>>>=20
>>> Hi,
>>>=20
>>> David Zuelke wrote:
>>>> Is this intentional? Related to opcache's "can only be built =
shared" status? But why would that trigger static builds? Or is it a =
bug?
>>>=20
>>> While we're at it, why is Opcache still built as shared? Does =
something prevent it being statically-linked?
>>=20
>> I remember something about PCRE and whether or not that's linked =
statically or not. Can't find it right now.
>>=20
>> Either way, it'd be great if someone in-the-know could chime in on =
this matter ;)
>=20
> Just a little *bump*... anyone got any idea here?
>=20
> Thanks!

And another *bump*... anyone from Zend maybe?