xfs
[Top] [All Lists]

libacl.lai vs. libacl.la in cmd/acl

To: XFS list <linux-xfs@xxxxxxxxxxx>
Subject: libacl.lai vs. libacl.la in cmd/acl
From: John Trostel <jtrostel@xxxxxxxxxxxxxx>
Date: Mon, 13 Aug 2001 15:59:33 -0400 (EDT)
Organization: Connex
Reply-to: John Trostel <jtrostel@xxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
When I make configure, make, make install on the ../cmd/acl directory in the
latest CVS of XFS, I get some warnings.  They look like this:

=== libacl ===
cd ../libacl/.libs; ../../install-sh -o root -g root -m 755 -d /lib;
../../install-sh -o root -g root -m 644 -T so_dot_version libacl.lai /lib; test
"SGI XFS" = debian || ../../install-sh -o root -g root -T so_dot_current
libacl.lai /lib
=== chacl ===
../install-sh -o root -g root -m 755 -d /bin
/usr/bin/libtool --mode=install ../install-sh -o root -g root -m 755 chacl /bin
libtool: install: warning: `../libacl/libacl.la' has not been installed in
`/lib'
../install-sh -o root -g root -m 755 .libs/chacl /bin/chacl

It's this warning about libacl.la not being installed in /lib that caught my
eye.  If I go back and manually install libacl.la (from the ../cmd/acl/libacl
directory) into /lib, I no longer get the warning.

My real question is why am I getting the warning?  Is it just my setup or is
there a problem with the make?

-- 
John M. Trostel
Senior Software Engineer
Quantum / SnapAppliances
jtrostel@xxxxxxxxxxxxxx


<Prev in Thread] Current Thread [Next in Thread>