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

 ID:                 52346
 Comment by:         jonasportugal at hotmail dot com
 Reported by:        huji dot huji at gmail dot com
 Summary:            cURL binary is bugous in 5.3.2 release for Windows
 Status:             Feedback
 Type:               Bug
 Package:            cURL related
 Operating System:   Windows XP
 PHP Version:        5.3.2
 Block user comment: N

 New Comment:

the problem is in version php 5.2.14


Previous Comments:
------------------------------------------------------------------------
[2010-10-21 16:57:29] [email protected]

Please try with 5.3.3.

------------------------------------------------------------------------
[2010-10-21 16:00:18] jonasportugal at hotmail dot com

I am having the same problem. The required DLLs are already in the PATH
of Environment Variables and the line for cURL is already uncommented in
php.ini



I've tried everything but nothing works.



PS: my OS is Win XP SP3

------------------------------------------------------------------------
[2010-07-15 12:32:30] huji dot huji at gmail dot com

Description:
------------
After installing a fresh copy of PHP 5.3.2 binaries for Windows
(extracted from php-5.3.2-Win32-VC6-x86.zip) as a module for Apache
2.2.4, and modifying php.ini to load some extensions (like GD2,
MBString, MySQL and MySQLi, and cURL), the cURL extension doesn't load
correctly.



Apache error log says:



PHP Warning:  PHP Startup: Unable to load dynamic library 'C:\\Program
Files\\PHP\\ext\\php_curl.dll' - The operating system cannot run %1.\r\n
in Unknown on line 0



On phpinfo(), all other loaded extensions are reported but cURL is not
loaded, hence not listed in phpinfo().





Expected result:
----------------
Expected result is successful loading of cURL extension.

Actual result:
--------------
cURL extension fails to load.


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



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

Reply via email to