Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91616
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.2 \(3112\))
In-Reply-To: <3F.65.03587.65DEED65@pb1.pair.com>
Date: Thu, 10 Mar 2016 16:56:00 +0100
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <0E11F160-CC0B-4161-AA35-9B7863A928D8@heroku.com>
References: <7D13E7EB-910D-42DD-ACF1-3872C1CE55C1@heroku.com> <3F.65.03587.65DEED65@pb1.pair.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 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?

I remember something about PCRE and whether or not that's linked =
statically or not. Can't find it right now.

Either way, it'd be great if someone in-the-know could chime in on this =
matter ;)

David