--0F1p//8PRICkK4MW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Jul 13, 2003 at 09:02:46AM -0700, ShieldX wrote:
> Ah yes, thank you, I knew I'd forgotten something,
> Here goes...
> I'm running  libgcc3.0-3.0.4-2mdk,
> gcc-c++-2.96-0.76mdk,
> gcc-2.96-0.76mdk,
> and gcc-cpp-2.96-0.76mdk
> on Mandrake 8.2 at present.
>=20
> I do not know if all those are relevant but they're some of the
> things that are on the dependencies list:
>=20
> [root@shredder clib]# ls
> glibc-2.3.2-5mdk.i586.rpm  libstdc++-devel-3.3-7.i386.rpm
> libstdc++-3.3-7.i386.rpm
> [root@shredder clib]# rpm -Uvh ./*
> error: failed dependencies:
>         initscripts < 6.91-18mdk conflicts with glibc-2.3.2-5mdk
>         libgcc_s.so.1(GCC_3.3)   is needed by libstdc++-3.3-7
>         glibc =3D 2.2.4 is needed by locales-2.3.1.2-8mdk
>         glibc =3D 2.2.4 is needed by locales-2.3.1.2-8mdk
>         glibc =3D 2.2.4 is needed by glibc-devel-2.2.4-25mdk
> [root@shredder clib]#

I am not sure where you obtained your RPMs, but did they have
instructions there?  Are they designed for Mandrake 8.2 or are they
simply copied out of a newer version?

As someone else pointed out, glibc is the core and can be dangerous to
upgrade.

Might I suggest you run `rpm -ivh ./*`?  Depending on how they were
packaged, I believe glibc 2.3.2 and 2.2.4 could live peacefully on the
same system.  In this case, your application would utilize the library
it requires while the rest of the system will stick with its
associated libraries.

--=20
                                                           Voltage Spike
      ,,,
     (. .)
--ooO-(_)-Ooo--

--0F1p//8PRICkK4MW
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/EwTBpNoctRtUIRQRArMDAJsGo0bl7TOMDmGMDcWuMslYNYw40gCeKyms
IgNmn9gd+IQ8Io3L8Vd5iRE=
=B0Yo
-----END PGP SIGNATURE-----

--0F1p//8PRICkK4MW--