topic Re: failed dependencies : libc.so.6(GLIBC_2.0) in Operating System - Linux

failed dependencies : libc.so.6(GLIBC_2.0)

Amit Dixit_2 — Sat, 13 Dec 2003 04:45:16 GMT

Hi,
I want to backup my entire system using mond-
mindi. For that it is asking me to prepare
the system i.e. it is asking me to install
few packages on to my system like cdrecord,
afio, buffer etc.

I have downloaded the packages but when i
try to install these packages it gives me
error

failed dependencies : libc.so.6(GLIBC_2.0)

What should i do, i checked glibc is already
there on my system and the library libc.so.6
is in the /lib folder maybe it is unable to
get the path..

Thanks,
AMit.

Re: failed dependencies : libc.so.6(GLIBC_2.0)

Oliver Charni — Sat, 13 Dec 2003 05:19:55 GMT

Hi!

Try this:
ldd $EXECUTABLE
It should give you an Output something like this:
root@wp001345 /usr/sbin #ldd xinetd
libwrap.so.0 => /usr/lib/libwrap.so.0 (0x40027000)
libnsl.so.1 => /lib/libnsl.so.1 (0x40030000)
libm.so.6 => /lib/tls/libm.so.6 (0x40045000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x40068000)
libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

This way you can tell where he looks for the Lib.

regards
oliver

Re: failed dependencies : libc.so.6(GLIBC_2.0)

Huc_1 — Sat, 13 Dec 2003 07:40:10 GMT

Amit,

I dont think RedHat 5.2 is supported, have a look at the following link.

http://www.microwerks.net/~hugo/support/support.html

It seems RedHat 6.0 is the entry point.

J-P

Re: failed dependencies : libc.so.6(GLIBC_2.0)

Amit Dixit_2 — Sat, 13 Dec 2003 13:35:17 GMT

Hi,
I gave the command
#ldd $EXECUTATBLE
it is saying
type ldd --help for usage

what should i do, i need to install few pacakages to get mondo-mindi work for me on my linux please help out for this
tell me how should i set the library path even when i try to install glibc-2.0.7-29.-386.rpm it syas library conflict and then comes out please tell me the solution for the same.

thanks,
amit

Re: failed dependencies : libc.so.6(GLIBC_2.0)

Martin P.J. Zinser — Sat, 13 Dec 2003 14:17:04 GMT

Hello Amit,

you will not like my reply I fear. First the
easy part

the command you need to type is ldd
where you do have to replace with the name of the program you want to inspect.

Now the bad news. Upgrading glibc is a major issue, it will cause lots and lots of other stuff to break resp. need to be upgraded. You best bet really would be to upgrade you RH system from 5.2 to a more current release. Since you are behind that far, this most probably will not be a one step process, but will involve intermediary releases. Details on the supported upgrade paths should be on the RH website.

Actually it might be easier to setup a system completely new from scratch with a current version and just to migrate the user and config files.

Gretings, Martin

Re: failed dependencies : libc.so.6(GLIBC_2.0)

Amit Dixit_2 — Sun, 14 Dec 2003 06:41:16 GMT

HI,
Martin i am installing that tools to take
backup of my entire system so that i can
upgrade it and for that i am facing this
problem of glibc when i try to install
cdrecord and afio, etc etc.

Thanks,
Amit

Re: failed dependencies : libc.so.6(GLIBC_2.0)

Bob_176 — Sun, 14 Dec 2003 10:23:24 GMT

You might try obtaining the .src.rpm's
and rebuild them against your current
libraries. Then roughly:
rpm -ivh mondo-1.47-3.rh7.src.rpm
cd /usr/src/redhat
rpm -bb SPECS/mondo.spec
If all goes well, a binary should show
up in RPMS/i386. And do the same for mindi.
You might have to edit the .spec file to
adjust for your particular version of redhat.
Or .. try building and using the generic tarball.

Re: failed dependencies : libc.so.6(GLIBC_2.0)

Brad Kozak — Tue, 16 Dec 2003 15:51:05 GMT

Hi AMit,

Installing the latest compat-glibc-???? relevant to your system should fix that failed depenency.

HTH,

bk