Re: pear install fine, but pecl install not, on SuSE 10.0

On 2/14/06, Paul Gardiner <php@glidos.net> wrote: > From: "Pierre" <pierre.php@gmail.com> > > On Tue, 14 Feb 2006 13:19:51 -0000 > > php@glidos.net ("Paul Gardiner") wrote: > > > >> Thanks for the suggestion. Can't seem to make it work though. > >> > >> I was warned when uninstalling php4_pear that it was needed by > >> mod_php4_core, but I uninstalled it anyway leaving mod_php4_core > >> in place. > >> > >> The uninstall removed /usr/bin/pear, but left /usr/bin/pecl, so I > >> deleted the latter. > >> > >> /usr/share/php still had remnants of pear, but I left those alone. > >> > >> go-pear seemed to work fine; looked like it even reinstalled > >> the bits that the uninstall didn't get rid of. > > > > Yes it does that, no worry here :) > > > >> But still pecl wouldn't work. It complained about the memory > >> limit again, I added "-d memory-limit=-1" to the command, > > > > You should disable memory limit for the installar (cli php.ini) > > That's one of the other mysteries. Changing the memory limit > in php.ini seems to have no effect on the install. That's > why I added the "-d ..." to the command. suse installs different php.ini, be sure to use the correct one. do: php -i | grep php.ini to know which is used with CLI > >> and then it acted the same as reported above. > > > > Did you install php4-devel pacakges? > > Yeah, I had done previously to first posting. Without that, I was > getting reports of phpize being missing rather than failing. I cannot help more here unless you use standard php packages (source install). You are the fifth person only this week to report problems with suse php... All problems solved when they use a clean php install (from source). --Pierre