[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] PHP4 MySQL Raq2
- Subject: Re: [cobalt-users] PHP4 MySQL Raq2
- From: Pierre Chopot <pierre@xxxxxxxxxxx>
- Date: Wed Apr 25 22:28:29 2001
- Organization: Zapilou
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Hello List,
Thursday, April 26, 2001, 9:24:33 AM, you wrote:
GCK> Well, the last couple of days I have posted a few messages regaurding PHP4
GCK> and Raq2, but I haven't really gotten any response on it. I've searched all
GCK> over the list, and there has been people that have said that had
GCK> successfully installed both php4 and mysql on raq2, but I have followed all
GCK> directions. I have compiled php4 a bunch of times, as DSO's, I have
GCK> compiled a new apache, and nothing. Everything seems to work fine, but I
GCK> when I try to start apache, it just dies, doesn't give me any errors, or
GCK> anything. If you look at the error log the only thing on there is (httpd:
GCK> caught SIGTERM, shutting down) That happens on both a DSO install with the
GCK> current apache, and with a new build apache. I don't know what is causing
GCK> it, but as soon as I remove the libphp4.so from httpd.conf, it will start up
GCK> (in DSO only) I hope someone can respond with some helpfull hints. I'm
GCK> using the latest version of MySQL, and PHP4. When I recompiled apache, I
GCK> used both 1.3.9 and 1.3.19, both with the same outcome.
GCK> Help Help Help
GCK> This is so frustrating.
GCK> :)
Yes, it is... I already answered you and Jay answered you as well. I
told you there is another thread with a similar subject and in that
thread I told people where to look: bugs.php.net bug id 9827
You have to modify something in crypt.c if you want to install PHP4
above 4.0.3 on a MIPS processor machine. I also offered you a small
howto (I'll send it off list to your address), as I said before it's
for a Qube2 (same processor) but you should be able to get it to work
for a Raq2.
--
Regards,
Pierre
pierre@xxxxxxxxxxx