ID: 24075 Updated by: [EMAIL PROTECTED] Reported By: Sven dot Schnitzke at t-online dot de Status: Open -Bug Type: PEAR related +Bug Type: *General Issues Operating System: WIN98SE PHP Version: 4.3.2 New Comment:
<Sorry, the problem was in go-pear.php. It tries to invoke php.exe -v to learn something of the returned string. With my inst the cli version of php is supposed to be invoked via PIF and cannot be launched directly via exec. It was this 'inner' call that issued the complaints about the missing dlls.> It tries to detect the current SAPI. Why do you use a pif do launch php? Then I do not know what is related with PEAR if php launched with a pif does not find some dlls. Comments? btw, have you think about moving to real OS? like something newer than win98se? win2K? pierre Previous Comments: ------------------------------------------------------------------------ [2003-06-09 08:18:15] [EMAIL PROTECTED] I've no idea what PHP 4.4-dev is..last release is 4.3.2.. Reclassified as pear bug. ------------------------------------------------------------------------ [2003-06-09 03:36:18] Sven dot Schnitzke at t-online dot de (IMHO the reason for this trouble is that relative extension dir spec is based upon cwd whereas it should be based upon the folder php resides in). Sorry, the problem was in go-pear.php. It tries to invoke php.exe -v to learn something of the returned string. With my inst the cli version of php is supposed to be invoked via PIF and cannot be launched directly via exec. It was this 'inner' call that issued the complaints about the missing dlls. Obviously with absolute path spec this call finds the extensions and everything is fine. Still don't know why e.g. a PHP4.4-dev (feb03 approx) works with relative specs? ------------------------------------------------------------------------ [2003-06-07 11:25:04] Sven dot Schnitzke at t-online dot de Yes, I am 100% sure. Meanwhile I verified that an absolute path spec does work. It is _really_ strange: curiously I tried go_pear.php and I encounter the named problem. When executing other scripts this is not the case. There is another strange thing about go_pear.php: it thinks I am using cgi while I am using php4apache. I tried go_pear with a PHP 4.4-dev and it worked (with some minor gliches) !?!? I will investigate further. It seems it could be a pear issue. ------------------------------------------------------------------------ [2003-06-07 04:50:23] [EMAIL PROTECTED] Are you 100% sure you have really updated PHP and that you don't have duplicate php4ts.dll's in your system? And that the one you have is for PHP 4.3.2? And FYI: earlier extensions might not work with current php. ------------------------------------------------------------------------ [2003-06-07 03:49:11] Sven dot Schnitzke at t-online dot de I just downloaded PHP-4.3.2 final and wanted to install it. (extension dir is specified as ..\php\extensions) I have parallel folders with some versions of PHP4 from 4.0.6 thru 4.3.2-RC and some snapshot 4.4-dev which I arranged to have at hand by just copying PHP.INI to the Apache folder and renaming the PHP folder to be the one supposed to hold the active PHP. No parts of PHP outside these folders except some two PIFS used to start PHP from the command line. This works because the Apache folder and the active PHP folder are parallel in the same tree. All versions I have work well this way including an earlier 4.3.2-RC. Now 4.3.2 final does not! IMHO copying the extensions to the WINSYS folder is not a viable way because a) it clutters WINSYS b) you are unable to quickly go forth (and back in case of trouble) with upgrading PHP Maybe absolute path works but I don't think it is a good idea to have a lot of places where absolute path specs are required. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=24075&edit=1
