ls: /lib/libattr.so.1: no version information available (required by /lib/libacl.so.1)

Linux and Unix-Like Red Hat
1

Hello,
I'm experimenting a problem on my rh server.

Red Hat Enterprise Linux AS release 3 (Taroon Update 8)
2.4.21-47.ELsmp #1 SMP i686 i686 i386 GNU/Linux

It started with a segmentation fault on

#id root

To resolve it, I've installed

coreutils-4.5.3-28.4.i386.rpm

But, I encountered a new issue. Everytime I do a ls or mv command I obtain this warning (commands works fine) :

# ls
ls: /lib/libattr.so.1: no version information available (required by /lib/libacl.so.1)

Some suggestions on how to resolve version problems?

Best Regards
gb

2

Hello,

libattr library is a shared library used by these binaries ls,mv. You need to have this shared library in the /usr/lib/ and a symlink known by libattr.so pointing to libattr.so.x where x is a number.
So do this.

find /usr -iname 'libattr*' -type f

If you see the results, then you have to have a symlink as specified above.

Please let me know,

Regards,
gaurav.

3

uhm... it is still not working

I've created simbolic links in /lib and /usr... but I've still the same error

Some suggestions?

PS: the library is stored in /lib not /usr/lib

4

Hello,

List the files in /lib

cd /lib&& ls -l libattr*
5 
# cd /lib&& ls -l libattr*
ls: /lib/libattr.so.1: no version information available (required by /lib/libacl.so.1)
lrwxrwxrwx    1 root     root           16 Mar 24 17:57 libattr.so.1 -> libattr.so.1.0.1
-rwxr-xr-x    2 root     root         7148 Jan 29  2003 libattr.so.1.0.1

# cd /lib&& ls -l libacl*
ls: /lib/libattr.so.1: no version information available (required by /lib/libacl.so.1)
lrwxrwxrwx    1 root     root           20 Mar 24 13:09 libacl.so.1 -> /lib/libacl.so.1.1.0
-rwxr-xr-x    2 root     root       371409 Jan 12  2006 libacl.so.1.1.0
6

Hello,

That looks okay
what does

ldd /bin/ls

to check for the dependancy of the shared libs

Apparently you do re-install those binaries(mv,ls) to resolve the version issue. The package manager 'yum' can take care of it.

Regards,
Gaurav.

7

Hello gaurav1086,
thanks for your support.

Finally I've found the problem. The coreutils update used wasn't the right one.

Now, with

rpm -Uvh  coreutils-4.5.3-28.7.i386.rpm

everything is right.

br
gb