Date: Wed, 2 Jul 2003 09:14:22 +1000
From: Nathan Scott <nathans@sgi.com>
To: linux-xfs@oss.sgi.com
Subject: Re: library errors building XFS tools...
Message-ID: <20030701231422.GC752@frodo>
References: <20030628213811.GA5436@widomaker.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030628213811.GA5436@widomaker.com>
User-Agent: Mutt/1.5.3i
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
Precedence: bulk

On Sat, Jun 28, 2003 at 05:38:14PM -0400, Charles Shannon Hendrix wrote:
> 
> 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...

Some distributions require this.

> 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
> /lib/libdm.so ../librmt/.libs/librmt.al
> 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>,

Hmm... are we missing a libtool flag perhaps?  (Why "should be"?)

> secondly, none of the libraries appears to be installed properly.

How are you doing the build/install (exact command sequence)?

> 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

You should definately not have to do that.  Are you doing a manual
"configure"?  See doc/INSTALL for recommended build steps.

> Here are the OS and tool versions I'm using:
> 
> Slackware 9.0 with a 2.4.20-xfs kernel
> 
> attr-2.2.0
> dmapi-2.0.5
> xfsdump-2.2.6
> xfsprogs-2.3.9
> 
> autoconf-2.57
> automake-1.7.3
> 

cheers.

-- 
Nathan