Home > Archive > PHP SQL > March 2005 > 7 days of pain, failed to upgrade to php 5.03 and MySQL 4.1 :(
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
7 days of pain, failed to upgrade to php 5.03 and MySQL 4.1 :(
|
|
| news.free.fr 2005-03-04, 8:56 pm |
| Hello,
I'm really lost: I'm stuck with an upgrade of mysql 4.1 & php 5.0.3 .
I m' working on a RedHat Linux 3.0 box with apache / httpd-2.0.46-25.ent.
Here is my case:
- Firstly, I've upgraded from MySQL 3.23 to MySQL 4.1
(MySQL-client-4.1.10-0.i386) => All was working fine...
- Secondly, I've upgraded from php (xxx) to php 5.0.3 (the last version, in
fact) => All was working fine...
And then, with hope :) I try to load a php/mysql web page. Alas... My php
installation seems to refuse to load my "mySQL module" (mysql.so seems to be
forgotten...).
In fact, the "mysql.ini" file is correctly identified by the php.ini
starting process, and appears in the "version();" function of apache (within
the "additional .ini files parsed" section), BUT, without the related "MySQL
information section"...
And consequently... all MySQL functions aren't working.
Turning a little around this problem, finally It appears that, (perhaps),
it's because I've previously forced the installation of the php-mysql lib
( php-mysql-5.0.3-1.0.rhel3.ct.i386.rpm) using the "--nodeps" tag.
Otherwise an error appears:
# rpm -ivh php-mysql-5.0.3-1.0.rhel3.ct.i386.rpm
error: Failed dependencies:
libmysqlclient.so.10 is needed by php-mysql-5.0.3-1.0.rhel3.ct
Suggested resolutions:
mysql-3.23.58-1.i386.rpm
And there it is my question : Why php 5 want to drive me back to MySQL 3.23
???!! Strange...
To be "compliant", if I try to re-install mySQL 3.23 (the package as
indicated there), I'm logically drived to this error:
# rpm -ivh mysql-3.23.58-1.i386.rpm
error: Failed dependencies:
/usr/local/bin/perl is needed by mysql-3.23.58-1
MySQL conflicts with mysql-3.23.58-1
(MySQL is already installed as I stated).
Help, please !!
Thx for all,
michael
| |
| HawkEye 2005-03-04, 8:56 pm |
| news.free.fr wrote:
> Hello,
>
> I'm really lost: I'm stuck with an upgrade of mysql 4.1 & php 5.0.3 .
>
> I m' working on a RedHat Linux 3.0 box with apache / httpd-2.0.46-25.ent.
>
> Here is my case:
>
> - Firstly, I've upgraded from MySQL 3.23 to MySQL 4.1
> (MySQL-client-4.1.10-0.i386) => All was working fine...
> - Secondly, I've upgraded from php (xxx) to php 5.0.3 (the last version, in
> fact) => All was working fine...
>
> And then, with hope :) I try to load a php/mysql web page. Alas... My php
> installation seems to refuse to load my "mySQL module" (mysql.so seems to be
> forgotten...).
>
> In fact, the "mysql.ini" file is correctly identified by the php.ini
> starting process, and appears in the "version();" function of apache (within
> the "additional .ini files parsed" section), BUT, without the related "MySQL
> information section"...
> And consequently... all MySQL functions aren't working.
>
> Turning a little around this problem, finally It appears that, (perhaps),
> it's because I've previously forced the installation of the php-mysql lib
> ( php-mysql-5.0.3-1.0.rhel3.ct.i386.rpm) using the "--nodeps" tag.
> Otherwise an error appears:
>
> # rpm -ivh php-mysql-5.0.3-1.0.rhel3.ct.i386.rpm
>
> error: Failed dependencies:
> libmysqlclient.so.10 is needed by php-mysql-5.0.3-1.0.rhel3.ct
> Suggested resolutions:
> mysql-3.23.58-1.i386.rpm
>
> And there it is my question : Why php 5 want to drive me back to MySQL 3.23
> ???!! Strange...
>
> To be "compliant", if I try to re-install mySQL 3.23 (the package as
> indicated there), I'm logically drived to this error:
>
> # rpm -ivh mysql-3.23.58-1.i386.rpm
> error: Failed dependencies:
> /usr/local/bin/perl is needed by mysql-3.23.58-1
> MySQL conflicts with mysql-3.23.58-1
> (MySQL is already installed as I stated).
>
> Help, please !!
> Thx for all,
> michael
>
>
>
The reason your scripts failed when you had php 5 and MySQL 4.1 is you can
no longer use the standard MySQL method in php from MySQl 4.1 onwards. You
now how to use the MySQLi method, for which the syntax is slightly
different. I don't have the details here as I haven't messed with it
myself because of this but there is information available on the web.
HTH
--
Regards
Neil
Registered Linux User 324599
| |
| Andy Hassall 2005-03-05, 3:57 am |
| On Fri, 04 Mar 2005 22:38:01 +0000, HawkEye <sunbed@rocketmail.com> wrote:
>The reason your scripts failed when you had php 5 and MySQL 4.1 is you can
>no longer use the standard MySQL method in php from MySQl 4.1 onwards. You
>now how to use the MySQLi method
No, not true, you can use the standard MySQL extension against MySQL 4.1.
MySQLi gives you access to the additional features in MySQL 4.1 but they
haven't disabled the old method.
--
Andy Hassall / <andy@andyh.co.uk> / <http://www.andyh.co.uk>
<http://www.andyhsoftware.co.uk/space> Space: disk usage analysis tool
| |
| HawkEye 2005-03-05, 3:57 pm |
| Andy Hassall wrote:
> On Fri, 04 Mar 2005 22:38:01 +0000, HawkEye <sunbed@rocketmail.com> wrote:
>
>
>
>
> No, not true, you can use the standard MySQL extension against MySQL 4.1.
> MySQLi gives you access to the additional features in MySQL 4.1 but they
> haven't disabled the old method.
>
AFAIKnew the old module in php 5 is for pre MySQL 4.1 versions and the
MySQLi module is for the new one. Thats why they made such a big deal of
the new client. However if the old system support is still available I
will be testing it soon :) Thnx for the info but sorry i can't help u with
your problem then :(
--
Regards
Neil
Registered Linux User 324599
| |
|
| Andy Hassall wrote:
> On Fri, 04 Mar 2005 22:38:01 +0000, HawkEye <sunbed@rocketmail.com> wrote:
>
>
>
>
> No, not true, you can use the standard MySQL extension against MySQL 4.1.
> MySQLi gives you access to the additional features in MySQL 4.1 but they
> haven't disabled the old method.
>
Ermm, version 5 of php stopped including the headers needed for building
a version of php and MySQL built from source. I think this is where you
could be experiencing a problem. Try rebuilding MySQL and then
rebuilding PHP
|
|
|
|
|