ID:               25176
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
-Status:           Verified
+Status:           Assigned
 Bug Type:         Zend Engine 2 problem
 Operating System: WinXP Pro SP1
 PHP Version:      5CVS-2003-08-20 (dev)
-Assigned To:      
+Assigned To:      zeev
 New Comment:

Zeev, you touched that stuff on 18th of August..



Previous Comments:
------------------------------------------------------------------------

[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.

------------------------------------------------------------------------

[2003-08-20 07:48:17] [EMAIL PROTECTED]

Description:
------------
Running the CLI (with or without flags or input) always brings up the
error:

The procedure entry point _zend_hash_init could not be located in the
dynamic link library php4ts.dll.

- Davey

Reproduce code:
---------------
C:\web\test>c:\php5\cli\php.exe -v [enter]
[error]
C:\web\test>

Expected result:
----------------
C:\web\test>c:\php5\cli\php.exe -v [enter]
PHP 5.0.0b2-dev (cli) (built: Aug 20 2003 12:10:03)
Copyright (c) 1997-2003 The PHP Group
Zend Engine v2.0.0-dev, Copyright (c) 1998-2003 Zend Technologies

C:\web\test>

Actual result:
--------------
Error message pops up with error "The procedure entry point
_zend_hash_init could not be located in the dynamic link library
php4ts.dll."


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=25176&edit=1

Reply via email to