On Sunday 19 January 2003 05:25 am, Aaron Mehl wrote: > Hi I saw the post and downloaded the mdbtools only to find it needs > glibc to be exact glibc-common-2.3.1-36.i386. > If I hunt up an rpm and install what could happen to my system? > I am a bit afraid to do this without urpmi but I don't see it using this > tool. > > > Since this is not the only thing I do I would hate to break all my apps > for this one??? > Aaron [tester@ibm333 tester]$ rpm -qa|grep glibc glibc-devel-2.2.5-16mdk glibc_lsb-2.2.90-11mdk glibc-i18ndata-2.2.5-16mdk glibc-2.2.5-16mdk [tester@ibm333 tester]$
That is from 9.0 normally a new level of glibc means binary incompatibility of rpms, and while Mandrake has a library naming protocol to allow multiple versions of ost libraries to be loaded and coexist, this is NOT true for glibc Download instead the source and compile it yourself that is, mdbtools-0.5.tar.gz I did not check the version for 9.1 beta but I am betting it will be the right one for the rpms. Dpkgs, binary tarballs, and rpms all fall when glibc changes significantly, and usually a twitch in the second number means exactly that. Civileme
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
