Thanks everyone - it now all goes !
The problem I think was due to using a precompiled binary release of Apache
that (I guess) had an exports file pointing to a library in the wrong place...
Anyway building everything from sources did the job.
Dave
At 23:36 20/05/01 -0400, you wrote:
Hmm.
Well we now have Apache 1.3.19 and PHP 4.0.5 but still the same problem...
Am about to upgrade MySQL to 3.23.38 to see if this changes things, but
feel this is clutching at straws...
Thanks,
Dave
On Thursday, May 17, 2001, at 08:59 AM, Matthew P. Marino wrote:
Apache is up to 1.3.17
MySQL 3.23.38 made no difference
Well we now have Apache 1.3.19 and PHP 4.0.5 but still the same problem...
Am about to upgrade MySQL to 3.23.38 to see if this changes things, but
feel this is clutching at straws...
Thanks,
Dave
On Thursday, May 17, 2001, at 08:59 AM,
Hmm. Can you be a bit more specific how you upgraded your Apache?
Typically I've had good luck with building the new Apache first, then
building PHP (using the new apxs that it installs). You are installing
these modules as .so, correct? And building everything from source
code? The only
Hello,
I am trying to port a PHP/MySQL application that happily runs under Linux
across to an AIX box.
We have MySQL is running under AIX - using mysql we can create tables,
insert rows, etc and even access data via a C program.
PHP is running as an Apache module - a simple phpinfo() works.
1.3.19 actually, Matt :) I'm running .19 on both my Linux machine and
the G4. And as far as I can remember, PHP4.0.4pl1 worked ok on 1.3.14,
I was doing that for a while.
Z
On Thursday, May 17, 2001, at 08:59 AM, Matthew P. Marino wrote:
Apache is up to 1.3.17 at least. I would update
These guys work way to fast for me. I'm used to companies that go years between
revisions and have a world wide webcast to mark the event. I stand humbly
corrected. Though on solaris, I couldn't get 4.0.4 to work with 1.3.14. The
point is, it's always best to be current!!
Zachary Burnham wrote:
