we where hoping to avoid all that, if possible :) it's not much of a product
server anymore, just for some small developement.
I guess we'll stick with what's installed.
Mike
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <mysql@lists.mysql.com>
Sent: Friday, April 21, 2006 5:38 PM
Subject: RE: Older version MySQL
You might like to take a look at smart package manager.
It's a wizz at dealing with dependancy conflicts.
http://labix.org/smart
http://wiki.suselinuxsupport.de/wikka.php?wakka=HowtoSmartPackageManager
http://forums.suselinuxsupport.de/index.php?showtopic=21121
HTH
Keith
In theory, theory and practice are the same;
in practice they are not.
On Fri, 21 Apr 2006, Nicolas Verhaeghe wrote:
To: 'Mike Blezien' <[EMAIL PROTECTED]>,
'MySQL List' <mysql@lists.mysql.com>
From: Nicolas Verhaeghe <[EMAIL PROTECTED]>
Subject: RE: Older version MySQL
Dependency issue, I would use RPM Package Manager.
It always solved that type of issue.
http://www.rpm.org/
-----Original Message-----
From: Mike Blezien [mailto:[EMAIL PROTECTED]
Sent: Friday, April 21, 2006 3:17 PM
To: MySQL List
Subject: Older version MySQL
Hello,
I am attempting to upgrade one of our older servers running RH 7.3
w/glibc-2.2.5-44
it's currently using 3.23.58 and tried installing 4.0.26 rpm's for linux,
but
won't install due to the following error:
libc.so.6(GLIBC_2.3) is needed by MySQL-shared-4.0.26-0
libpthread.so.0(GLIBC_2.3.2) is needed by MySQL-shared-4.0.26-0
libc.so.6(GLIBC_2.3) is needed by MySQL-shared-compat-4.0.26-0
libpthread.so.0(GLIBC_2.3.2) is needed by
MySQL-shared-compat-4.0.26-0
Now of the RPM's will install. Is there a 4.0.+ version that will install on
this type of server without have to upgrade alot of other
stuff ?? Or can we
build it from source, and if so, what is the recommend configure options
used to
build from source ?
TIA,
Mike(mickalo)Blezien
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
