#30637 [Opn]: compile with pear error
| From: | arthur at mir5 dot homeip dot net | Date: | Tue, 02 Nov 2004 02:13:43 +0000 |
| Subject: | #30637 [Opn]: compile with pear error | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-68607@lists.php.net to get a copy of this message | ||
ID: 30637
User updated by: arthur at mir5 dot homeip dot net
Reported By: arthur at mir5 dot homeip dot net
Status: Open
Bug Type: Compile Failure
Operating System: (Slackware) linux-2.4.25
PHP Version: 5.0.2
New Comment:
any reason your not trying php 5.0.2?
Previous Comments:
------------------------------------------------------------------------
[2004-11-02 03:06:44] robbat2 at gentoo dot org
after setting up php-4.3.9 on another machine today and having it work
perfectly fine, I tried something on a hunch - found that php-4.3.9
compiled and installed perfectly fine after a reboot, but then didn't
want to install properly after that, until I rebooted the machine
again.
I'm going to pursue other angles of what could be the problem.
------------------------------------------------------------------------
[2004-11-01 22:36:53] arthur at mir5 dot homeip dot net
php-5.0.2/pear# valgrind -v --tool=memcheck php ./install-pear.php
http://mir5.homeip.net:8080/bugs/valgrindcheck.txt
------------------------------------------------------------------------
[2004-11-01 21:05:35] derick@php.net
valgrind --tool=memcheck php ./script-that-crashes.php
should do it.
------------------------------------------------------------------------
[2004-11-01 19:47:06] arthur at mir5 dot homeip dot net
please tell me exactly what you want me to run.
valgrind php ./install-pear.php
you must give it a tool= option.
also what flags should i include.
------------------------------------------------------------------------
[2004-11-01 10:40:08] robbat2 at gentoo dot org
valgrind output:
http://dev.gentoo.org/~robbat2/php-4.3.9-valgrind.trace
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/30637
--
Edit this bug report at http://bugs.php.net/?id=30637&edit=1