PHP Pear - PEAR broken on current Mac OS on PowerPC?

Author

PEAR broken on current Mac OS on PowerPC?

David Gurney

2006-10-30, 7:07 pm

Hi all.

I didn't see this in the archives.

I've built PHP 5.1.6 on three Macs now, one Intel and two PowerPC, under OS
10.4.8. The Intel experience went fine.

Things are broken on PowerPC. Both systems previously had only the stock
PHP4 that comes with OS X, and it was not activated. PEAR consistently
fails during "make install" of PHP5 with the following message:

Installing PEAR environment: /Library/PHP5/lib/php/
php(17633) malloc: *** vm_allocate(size=3825205248) failed (error code=3)
php(17633) malloc: *** error: can't allocate region
php(17633) malloc: *** set a breakpoint in szone_error to debug
make[1]: *** [install-pear-installer] Segmentation fault
make: *** [install-pear] Error 2

I used the go-pear script, which appeared to complete fine and reported
version 1.4.1. But it made no difference.

Any ideas? Thanks!

Gavin

________________________________________
_________________________
Find a local pizza place, music store, museum and more…then map the best
route! http://local.live.com?FORM=MGA001

Gregory Beaver

2006-10-30, 7:07 pm

David Gurney wrote:
> Hi all.
>
> I didn't see this in the archives.
>
> I've built PHP 5.1.6 on three Macs now, one Intel and two PowerPC, under
> OS 10.4.8. The Intel experience went fine.
>
> Things are broken on PowerPC. Both systems previously had only the
> stock PHP4 that comes with OS X, and it was not activated. PEAR
> consistently fails during "make install" of PHP5 with the following
> message:
>
> Installing PEAR environment: /Library/PHP5/lib/php/
> php(17633) malloc: *** vm_allocate(size=3825205248) failed (error code=3)
> php(17633) malloc: *** error: can't allocate region
> php(17633) malloc: *** set a breakpoint in szone_error to debug
> make[1]: *** [install-pear-installer] Segmentation fault
> make: *** [install-pear] Error 2
>
> I used the go-pear script, which appeared to complete fine and reported
> version 1.4.1. But it made no difference.
>
> Any ideas? Thanks!

This is a php error, perhaps a problem in your configuration line, but
it looks more serious. I would suggest building php with --enable-debug
and --disable-zend-memory-manager options, then when the fatal error
happens, you'll get a dump that can be used with gdb to grab a
backtrace. When you get that, report it to php-internals and see what
they have to say.

Thanks,
Greg

Sponsored Links