php-windows Digest 15 Jul 2013 20:49:27 -0000 Issue 4112
Topics (messages 31041 through 31043):
Re: Running more PHP-versions with php_opcache.dll
31041 by: Pierre Joye
31042 by: Jan Ehrhardt
31043 by: Pierre Joye
Administrivia:
To subscribe to the digest, e-mail:
php-windows-digest-subscr...@lists.php.net
To unsubscribe from the digest, e-mail:
php-windows-digest-unsubscr...@lists.php.net
To post to the list, e-mail:
php-wind...@lists.php.net
----------------------------------------------------------------------
--- Begin Message ---
hi,
On Wed, Jul 10, 2013 at 10:28 AM, Jan Ehrhardt <php...@ehrhardt.nl> wrote:
> Jan Ehrhardt in php.windows (Tue, 09 Jul 2013 23:11:36 +0200):
>>Pierre Joye in php.windows (Tue, 9 Jul 2013 22:39:17 +0200):
>>>I do not understand why you build everything from scratch. Providing the
>>>missing ext should be enough. Also we work with everyone to be sure that we
>>>are all sync'ed from a VC version POV. There should not be a need to
>>>provide custom build for php itself. But that's another discussion.
>>
>>It started with something PHP.net did not deliver: x64 versions of PHP
>>5.3 and 5.4. And for me it is the easiest way to keep up-to-date. A
>>single build script for all extensions, with a direct check if they
>>load. But you are right: that is another discussion.
>
> What php.net also did not deliver was versions with openssl 1.x.
> I switched to that early because of this problem with curl and openssl
> 0.9.8h+: http://sourceforge.net/p/curl/bugs/1037/#dfa4
>
> It might have been fixed 2 months ago:
> http://sourceforge.net/p/curl/bugs/1037/?page=3
We simply can't move to 1.x for any current stable versions (but 5.5
which has 1.x now). There are so many incompatibilities (both ABI and
API) and many 3rd parties extensions rely on openssl.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--- End Message ---
--- Begin Message ---
Hi Pierre,
Getting back on topic.
Jan Ehrhardt in php.windows (Tue, 09 Jul 2013 23:11:36 +0200):
>Steffen from Apachelounge said something interesting:
>"Opcache is creating in his temp dir ...."
>http://www.apachelounge.com/viewtopic.php?t=5461
I followed Steffen's idea to use FcgidInitialEnv to put the semaphore
file in another directory. No luck, because the OPcaches still seem to
currupt each other. See especially:
http://www.apachelounge.com/viewtopic.php?p=25124#25124
This must have something to do with the fixed X64 addresses, I think.
Jan
--- End Message ---
--- Begin Message ---
hi!
On Wed, Jul 10, 2013 at 4:42 PM, Jan Ehrhardt <php...@ehrhardt.nl> wrote:
> Hi Pierre,
>
> Getting back on topic.
>
> Jan Ehrhardt in php.windows (Tue, 09 Jul 2013 23:11:36 +0200):
>>Steffen from Apachelounge said something interesting:
>>"Opcache is creating in his temp dir ...."
>>http://www.apachelounge.com/viewtopic.php?t=5461
>
> I followed Steffen's idea to use FcgidInitialEnv to put the semaphore
> file in another directory. No luck, because the OPcaches still seem to
> currupt each other. See especially:
> http://www.apachelounge.com/viewtopic.php?p=25124#25124
>
> This must have something to do with the fixed X64 addresses, I think.
Btw, it would good if you could provide a backtrace or the log, in
case it does not actually crashes but raised a fatal error (which can
happen in case it failed to get a valid address, f.e.).
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--- End Message ---
