xfs
[Top] [All Lists]

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

To: linux-xfs@xxxxxxxxxxx
Subject: Re: libacl.lai vs. libacl.la in cmd/acl
From: Dean Roehrich <roehrich@xxxxxxx>
Date: Mon, 13 Aug 2001 15:23:28 -0500
Sender: owner-linux-xfs@xxxxxxxxxxx
>From:  John Trostel <jtrostel@xxxxxxxxxxxxxx>
>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; tes
>t
>"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 /bi
>n
>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?

It's not a problem.  The libacl.la hasn't been installed by that point, and
isn't needed by then, either.

By the time all the pieces are installed everything will be where it needs to
be.

Dean


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