yet another mod_php4 problem :-(
Will Mitayai Keeso Rowe
mit at dreamlabs.com
Mon Mar 31 01:46:41 PST 2003
to be more accurate, I should point out that I wiped my entire system
and started from scratch, so to answer your next question "No, there is
no trace left of Mysql 4 on my system" ;-)
From: Will Mitayai Keeso Rowe [mailto:mit at dreamlabs.com]
Sent: March 31, 2003 4:40 AM
To: 'Edwin Groothuis'
Cc: 'ports at freebsd.org'
Subject: RE: yet another mod_php4 problem :-(
I did, but there were so many compatibility problems I deinstalled it
and went back to 3.
From: Edwin Groothuis [mailto:edwin at mavetju.org]
Sent: March 31, 2003 4:16 AM
To: Will Mitayai Keeso Rowe
Cc: ports at freebsd.org
Subject: Re: yet another mod_php4 problem :-(
On Mon, Mar 31, 2003 at 03:57:59AM -0500, Will Mitayai Keeso Rowe wrote:
> Any idea what this could be caused by?
> Installing PHP CLI binary: /usr/local/bin/
> Installing PHP SAPI module
> [activating module `php4' in /usr/local/etc/apache/httpd.conf]
> cp libs/libphp4.so /usr/local/libexec/apache/libphp4.so
> chmod 755 /usr/local/libexec/apache/libphp4.so
> cp /usr/local/etc/apache/httpd.conf
> cp /usr/local/etc/apache/httpd.conf.new
> rm /usr/local/etc/apache/httpd.conf.new
> Installing shared extensions:
> Installing PEAR environment: /usr/local/lib/php/
> Segmentation fault (core dumped)
> *** Error code 139
You have MySQL 4?
Somebody here complained about the same problem this afternoon.
Edwin Groothuis | Personal website:
edwin at mavetju.org | Weblog:
More information about the freebsd-ports