Problems with PHP 5.3.0 RC1 VC6 x86 thread safe (and most probably with
the other versions too):
- php.ini-development and php.ini-production parse error on line 581
- php_mcrypt.dll not present as a file in ./ext
- php_mhash.dll, php_msql.dll and php_pspell.dll are present as an
option in php.ini although it is said they are removed - php_enchant.dll not present nor as an option in php.ini, nor as a file
in ./ext and I cannot see it in the php -m output - php_phar.dll present as an option in php.ini but there is no need
(causes confusion) - php_pdo.dll present as an option in php.ini but there is no need
(causes confusion)
Cheers
--
Ionut G. Stan
I'm under construction |http://igstan.blogspot.com/
hi,
Problems with PHP 5.3.0 RC1 VC6 x86 thread safe (and most probably with the
other versions too):
- php.ini-development and php.ini-production parse error on line 581
Eric, can you look at it please?
- php_mcrypt.dll not present as a file in ./ext
builtin
- php_mhash.dll, php_msql.dll and php_pspell.dll are present as an option in
php.ini although it is said they are removed
right, should be removed.
- php_phar.dll present as an option in php.ini but there is no need (causes
confusion)
not decided if it will be static or shared.
- php_pdo.dll present as an option in php.ini but there is no need (causes
confusion)
builtin
thanks for your feedbacks!
Cheers,
Pierre
Hi Pierre and Ionut:
- php.ini-development and php.ini-production parse error on line 581
Eric, can you look at it please?
That was fixed yesterday (per "php.ini-production & php.ini-development
last minute updates" thread).
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
That was fixed yesterday (per "php.ini-production& php.ini-development
last minute updates" thread).
Sorry, just saw it.
--
Ionut G. Stan
I'm under construction | http://igstan.blogspot.com/
2009/3/26 Ionut G. Stan ionut.g.stan@gmail.com:
That was fixed yesterday (per "php.ini-production& php.ini-development
last minute updates" thread).Sorry, just saw it.
Pierre just fixed the others except for phar in CVS, so the changes
will be in RC2 and thanks for the headsup =)
--
Ionut G. Stan
I'm under construction | http://igstan.blogspot.com/--
--
Kalle Sommer Nielsen
kalle@php.net
re,
To summarize:
Problems with PHP 5.3.0 RC1 VC6 x86 thread safe (and most probably with the
other versions too):
- php.ini-development and php.ini-production parse error on line 581
fixed
- php_mcrypt.dll not present as a file in ./ext
fixed
- php_mhash.dll, php_msql.dll and php_pspell.dll are present as an option in
php.ini although it is said they are removed
fixed
- php_enchant.dll not present nor as an option in php.ini, nor as a file in
./ext and I cannot see it in the php -m output
Only available for VC9 builds for now
- php_phar.dll present as an option in php.ini but there is no need (causes
confusion)
Will be change when we are sure of the built type (builtin or shared)
- php_pdo.dll present as an option in php.ini but there is no need (causes
confusion)
fixed
as well as all other having droped too in the past releasese.
cheers,
Pierre
Pierre Joye wrote:
- php_phar.dll present as an option in php.ini but there is no need (causes
confusion)Will be change when we are sure of the built type (builtin or shared)
What is the debate? Whether windows build should match unix build?
Greg
Hi Greg
2009/3/27 Greg Beaver greg@chiaraquartet.net:
Pierre Joye wrote:
- php_phar.dll present as an option in php.ini but there is no need (causes
confusion)Will be change when we are sure of the built type (builtin or shared)
What is the debate? Whether windows build should match unix build?
The question is that, should Phar be built staticlly or shared by
default in the Windows distro, as it is right now then Phar is built
staticlly and if its kept that way then extension=php_phar.dll will be
useless in php.ini.
Greg
--
--
Kalle Sommer Nielsen
kalle@php.net
Kalle Sommer Nielsen wrote:
Hi Greg
2009/3/27 Greg Beaver greg@chiaraquartet.net:
Pierre Joye wrote:
- php_phar.dll present as an option in php.ini but there is no need (causes
confusion)Will be change when we are sure of the built type (builtin or shared)
What is the debate? Whether windows build should match unix build?
The question is that, should Phar be built staticlly or shared by
default in the Windows distro, as it is right now then Phar is built
staticlly and if its kept that way then extension=php_phar.dll will be
useless in php.ini.
Hi,
My next question is why there is still debate on this question when the
question was settled by the RMs on internals on Nov. 18, 2008
http://marc.info/?l=php-internals&m=122684228317217&w=2
This is why I am asking - am I confused about the finality of this decision?
Greg