In <
a39ad6b5-39d4-6028...@ecomstation.it>, on 06/22/25
>but now, with:
>php composer.phar require guzzle/guzzle:~7.9.3
>the command do nothing and do not print out anything
It's obviously doing something. The CPU meter spikes. We just do not yet
know what it's doing on your system.
Use php --help to show the command line options. The -m and -i can be
useful for
On my php7 test setup, which does not have much installed, I get output.
php composer.phar version
outputs
Fatal error: Uncaught Error: Class 'Composer\XdebugHandler\XdebugHandler'
not found in
phar://I:\sla_dev2_browse\composer-shl\composer.phar/bin/composer:28 Stack
trace:
#0 I:\sla_dev2_browse\composer-shl\composer.phar(29): require() #1 {main}
thrown in
phar://I:\sla_dev2_browse\composer-shl\composer.phar/bin/composer on line
28
and
>php composer.phar require guzzle/guzzle:~7.9.3
outputs the same error
Fatal error: Uncaught Error: Class 'Composer\XdebugHandler\XdebugHandler'
not found in
phar://I:\sla_dev2_browse\composer-shl\composer.phar/bin/composer:28 Stack
trace:
#0 I:\sla_dev2_browse\composer-shl\composer.phar(29): require() #1 {main}
thrown in
phar://I:\sla_dev2_browse\composer-shl\composer.phar/bin/composer on line
28
Since you did not get any console output, dId you check for popuplog
entries?
My current understanding implies our builds may not have xdebug available,
but this can probably be worked around.
Based on the error message, I suspect there's a problem with slash
handling in phar files in our port.
I can't say whether or not it is related, but running under sh.exe
php -r '$phar = new Phar("composer.phar");
$phar->extractTo("./vendor",null,true);'
can extract files, but cannot create subdirectores.
I'll revist all of this as time permits amd test against php8.