ID: 25176
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Bogus
+Status: Open
Bug Type: Zend Engine 2 problem
Operating System: WinXP Pro SP1
PHP Version: 5CVS-2003-08-20 (dev)
Assigned To: zeev
New Comment:
Then there is something else at play here.
I keep my PHP installs in seperate folders like this:
c:\php4\
c:\php5\
I do not move php4ts.dll to system32 or anything, it should use the
php4ts.dll in the c:\php*\ folder depending on which binary I run (PHP4
or PHP5). It appears that php5 is *not* using the php4ts.dll in c:\php5
(note the cli binary is in c:\php5\cli\php.exe) and indeed when I
remove all other php4ts.dll's from my system I get:
"This application has failed to start because php4ts.dll was not found.
Re-installing the application may fix this problem."
I am now going to check which php4ts.dll it is detecting (I have quite
a few ;) and perhaps I can see why (i.e. if its the one from ZDE its
most likely that that .dll is registered with the OS and the one with
php5 is not, however PHP4 doesn't suffer from this, so something can be
done to fix this)
- Davey
Previous Comments:
[2003-08-20 18:12:54] [EMAIL PROTECTED]
edink hit it on the head - it's not a bug, you're mixing binaries from
different builds.
In Windows there's a simple rule - if it builds, there are no missing
symbols, they just can't exist. If there are missing symbols - the
build would fail.
The only situation where you can get missing symbols is if you mix
different successfully-built binaries.
[2003-08-20 17:55:04] [EMAIL PROTECTED]
Zeev, you touched that stuff on 18th of August..
[2003-08-20 16:31:28] [EMAIL PROTECTED]
I too also experienced this error in the php/php-cli dists. I also
must note that the internal socket support throws a starnge error in
the newer snaps as well.
~ Andrew
[2003-08-20 16:21:08] [EMAIL PROTECTED]
Uhm... php4ts.dll is what is in the win32 PHP5 zip file, with a version
of 5.0.0
- Davey
[2003-08-20 07:59:04] [EMAIL PROTECTED]
You mixed up .dlls from sever releases. Not a bug.
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/25176
--
Edit this bug report at http://bugs.php.net/?id=25176&edit=1
