Re: Trying to install PEAR is a Fr3@K!n nightmare
| From: | Terence Kearns | Date: | Wed, 18 Jun 2003 03:25:59 +0000 |
| Subject: | Re: Trying to install PEAR is a Fr3@K!n nightmare | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-6075@lists.php.net to get a copy of this message | ||
LIMBOURG Arnaud wrote:
I created an error log for php.ini and found that pear.php was exceeding timeout on line 631. This is somewhere in the vacinity of a dl() call (two lines below). When I added the line die(debug_backtrace()); just before the dl() call to foind out where the loadExtension() function was being called from, the pear.bat script "appeared" to work. In other words, when I ran pear install pear/HTTP-1.2.tgz it said everything was installed, when I went to the pear/HTTP directory it was empty. When I tried to re-run the same line, it said that HTTP was already installed. when i removed the debug line and ran it gain, it again said that it was already installed and the HTTP directory is *still* empty. All this is confirmed when attempting to include any of the files. I've just re-checked my pear.bat file and it seems to have been updated to a vastly different pear.bat file after I just re-ran go-pear (which I did just for the hell of it). So all the symptoms above (empty install dir) are based on this new pear.bat (which seems to use the same directory structure that I have).I inserted print statenments in likely places [I have previously asked how to trace php execution, and have had no response: can no-one tell me?] and traced the crash, (at least the crash from the command-line,) to execution of the statementTyr to install the xdebug extension http://xdebug.derickrethans.nl/link.php?url=xdebug120-43-win then add the following to your php.ini ; XDEBUG xdebug.default_enable = Onxdebug.auto_profile = Off xdebug.collect_params = OnTry to run go-pear.bat and not go-pear.php directly. Then come back :) Arnaud. The extension looks useful however I seem to be able to get adequate information from debug_backtrace() which does not seem to rquire any extenions in version 4.3.2