Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91533
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.49 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-ID: <7D13E7EB-910D-42DD-ACF1-3872C1CE55C1@heroku.com>
Date: Tue, 8 Mar 2016 02:57:31 +0100
To: PHP Developers Mailing List <internals@lists.php.net>
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Enabling opcache causes libraries to build as static
From: dz@heroku.com (David Zuelke)

Hi all,

I've been trying to get to the bottom of why even a minimal PHP build =
(any 5.x or 7 release, or a fresh e.g. 7.0 branch checkout after =
buildconf) creates .a versions of all shared extensions in addition to =
.so modules.

I've narrowed it down to opcache:

$ ./configure --disable-all
...
checking whether to build shared libraries... yes
checking whether to build static libraries... no

versus

$ ./configure --disable-all --enable-opcache=3Dshared
...
checking whether to build shared libraries... yes
checking whether to build static libraries... yes

but I cannot figure out why this is happening (both on OS X and Ubuntu =
14.04).

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?

I've been wading through config.m4s, generated configures etc but still =
haven't found the reason; any pointers or explanations would be much =
appreciated!

Cheers,

David