Re: Enabling opcache causes libraries to build as static
| From: | David Zuelke | Date: | Sun, 20 Mar 2016 21:10:17 +0000 |
| Subject: | Re: Enabling opcache causes libraries to build as static | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-91793@lists.php.net to get a copy of this message | ||
On 10.03.2016, at 16:56, David Zuelke <dz@heroku.com> wrote:
>
>> On 08.03.2016, at 16:18, Andrea Faulds <ajf@ajf.me> wrote:
>>
>> Hi,
>>
>> 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?
>>
>> 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 ;)
Just a little *bump*... anyone got any idea here?
Thanks!