You are not logged in.
- Topics: Active | Unanswered
#1 2009-10-07 13:08:42
- Skyscraper
- Member
- Registered: 2005-06-20
- Posts: 72
free: error while loading shared libraries: libproc-3.2.7.so: cannot o
ARCH CURRENT (and fresh)
==============
PROBLEM:
==============
# free
free: error while loading shared libraries: libproc-3.2.7.so: cannot open shared object file: No such file or directory
# locate libproc
/lib/libproc-3.2.8.so
==============
Temporary solution:
==============
# cd /lib/
# ln -s /lib/libproc-3.2.8.so libproc-3.2.7.so
Offline
#2 2009-10-08 03:23:54
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: free: error while loading shared libraries: libproc-3.2.7.so: cannot o
Normally I start off recommending strongly that you don't symlink anything, but this thread is strange enough to go a whole different way.
free, as I'm guessing that you already know, is part of procps. Where a library conflict is coming from is beyond me. What happens when you:
pacman -Qo /usr/bin/free
Offline
#3 2009-10-08 03:27:49
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,672
- Website
Re: free: error while loading shared libraries: libproc-3.2.7.so: cannot o
Or even, "which free". Both these come from the same package so free can not plausibly be build against another version of libproc...
On i686:
> readelf -d /usr/bin/free
Dynamic section at offset 0x147c contains 22 entries:
Tag Type Name/Value
0x00000001 (NEEDED) Shared library: [libproc-3.2.8.so]
0x00000001 (NEEDED) Shared library: [libc.so.6]Edit: same on x86_64....
Offline