RE: [PEAR] What is This Problem All About??

My setting is %PHP_BIN% -C -d output_buffer=0 -d include_path=%PEAR_PATH% -f %PEAR_PATH%\scripts\pear.in -- %1 %2 %3 %4 %5 %6 %7 %8 %9 So it calls pear.in and works perfectly. Note that output_buffering is 0 and not 1. The other way around is to rename pear.in to pear, put it into c:\php and modify the line as follows %PHP_BIN% -C -d output_buffer=0 -d include_path=%PEAR_PATH% -f %BIN_PATH%\pear -- %1 %2 %3 %4 %5 %6 %7 %8 %9 Arnaud. > Given my (possibly bad!) settings: > > set PHP_BIN=c:\php\cli\php.exe > set BIN_DIR=c:\php > set PEAR_PATH=c:\php\pear > > then when I run "pear.bat" the command line: > > %PHP_BIN% -C -d output_buffering=1 -d include_path=%PEAR_PATH% -f > %BIN_DIR%\pear -- %1 %2 %3 %4 %5 %6 %7 %8 %9 > > expands to: > > c:\php\cli\php.exe -C -d output_buffering=1 -d > include_path=c:\php\pear -f c:\php\pear -- > > which is meaningless because "c:\php\pear" isn't a PHP > script. Note however > that, because of > that "\pear" appended to "%BIN_DIR%" no sensible setting > would make the -f > argument point to "c:\php\pear\scripts\pear.in". Maybe it > would be correct > if it was a "\pear.in" -- but it's not. > > Bye > Michele