Description of problem:
The /usr/lib/libacl.la file from libacl-devel is broken.  It causes compilation
bugs like the following (found when compiling the development version of
gnome-vfs which just recently gained acl support):

/bin/sh ../libtool --tag=CC --mode=link gcc  -g -O2   -o libfile.la -rpath
/opt/gnome2/lib/gnome-vfs-2.0/modules -export_dynamic -avoid-version -module
-no-undefined file-method.lo fstype.lo file-method-acl.lo   -lattr -lacl -lfam
-pthread -L/opt/gnome2/lib -lgobject-2.0 -lgconf-2 -lORBit-2 -lm -lgmodule-2.0
-ldl -lgthread-2.0 -lglib-2.0 -liconv   ../libgnomevfs/libgnomevfs-2.la -lutil
-lrt -lrt
grep: /lib/libattr.la: No such file or directory
/bin/sed: can't read /lib/libattr.la: No such file or directory
libtool: link: `/lib/libattr.la' is not a valid libtool archive
make[2]: *** [libfile.la] Error 1
make[2]: Leaving directory `/export/home/b/newrenTemp/gnome/gnome-vfs/modules'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/export/home/b/newrenTemp/gnome/gnome-vfs'
make: *** [all] Error 2

Version-Release number of selected component (if applicable):
libacl-devel-2.2.23-5

How reproducible:
100%

Additional info:
This is caused by /usr/lib/libacl.la trying to refer to a file from
libattr-devel, but getting the path wrong.  The fix is trivial; just apply the
following patch

--- /usr/lib/libacl.la.orig      2004-09-16 14:34:23.000000000 -0600
+++ /usr/lib/libacl.la  2006-06-13 16:50:41.000000000 -0600
@@ -14,7 +14,7 @@
 old_library='libacl.a'

 # Libraries that this one depends upon.
-dependency_libs=' /lib/libattr.la'
+dependency_libs='/usr/lib/libattr.la'

 # Version information for libacl.
 current=2