Why does the xfs tool build mix library files between /lib and /usr/lib?
The shared objects in /lib, the libtool stuff in /usr/lib... this seems
to cause grief when building other xfs programs.
It would be much nicer if you could just give a single prefix for those
who want to store things in /usr/local, or somewhere else.
In any case, I build attr and xfsprogs using the defaults and linking in
xfsdump still fails:
p.o var.o /usr/lib/libuuid.a /lib/libhandle.so /lib/libattr.so
gcc: /lib/libhandle.so: No such file or directory
gcc: /lib/libattr.so: No such file or directory
gcc: /lib/libdm.so: No such file or directory
First of all, shared libraries should be linked with -llib<name>,
secondly, none of the libraries appears to be installed properly.
It seems like libtool is doing the wrong thing, and leaving out steps
like linking the .so files with the .so<version files.
I had to manually run this:
% cd /lib
% ln -s libattr.so.1 libattr.so
% ln -s libhandle.so.1 libhandle.so
% ln -s libdm.so.0 libdm.so
Here are the OS and tool versions I'm using:
Slackware 9.0 with a 2.4.20-xfs kernel
UNIX/Perl/C/Pizza____________________s h a n n o n@wido !SPAM maker.com