7:46 a.m.
On 07/16/18 14:20, Niels de Vos wrote:
On Mon, Jul 16, 2018 at 11:21:35AM +0200, patrice.lucas(a)cea.fr
wrote:
> I'm trying to update Ganesha CEA Continuous-Integration tests by setting a
> new configuration over FEDORA 28.
>
>
> I'm facing a first cmake error because the "attr/xattr.h" file seems
not to
> exist anymore in Fedora 28. This file is claimed by the gluster FSAL.
>
>
> Does anyone already compile the Gluster FSAL over Fedora 28 ?
>
>
> Should we remove the use of "attr/xattr.h" by the gluster fsal ? Which is
> the bast replacement for "attr/xattr.h" ?
You should be able to install libattr-devel and get the headers. It
should get pulled in when you install glusterfs-api-devel that is needed
for FSAL_GLUSTER.
HTH,
Niels
libattr-devel is installed but the /usr/include/attr/xattr.h is missing.
I'm still looking for an explanation of the following situation :
[root@vm0 ~]# dnf provides "/usr/include/attr/xattr.h"
Last metadata expiration check: 0:59:09 ago on Mon 16 Jul 2018 11:39:58
AM UTC.
libattr-devel-2.4.47-23.fc28.i686 : Files needed for building programs
with libattr
Repo : fedora
Matched from:
Filename : /usr/include/attr/xattr.h
libattr-devel-2.4.47-23.fc28.x86_64 : Files needed for building programs
with libattr
Repo : fedora
Matched from:
Filename : /usr/include/attr/xattr.h
[root@vm0 ~]#
[root@vm0 ~]#
[root@vm0 ~]# rpm -ql libattr-devel
/usr/include/attr
/usr/include/attr/attributes.h
/usr/include/attr/error_context.h
/usr/include/attr/libattr.h
/usr/lib64/libattr.so
/usr/lib64/pkgconfig/libattr.pc
/usr/share/man/man3/attr_get.3.gz
/usr/share/man/man3/attr_getf.3.gz
/usr/share/man/man3/attr_list.3.gz
/usr/share/man/man3/attr_listf.3.gz
/usr/share/man/man3/attr_multi.3.gz
/usr/share/man/man3/attr_multif.3.gz
/usr/share/man/man3/attr_remove.3.gz
/usr/share/man/man3/attr_removef.3.gz
/usr/share/man/man3/attr_set.3.gz
/usr/share/man/man3/attr_setf.3.gz
[root@vm0 ~]# rpm -q libattr-devel
libattr-devel-2.4.48-1.fc28.x86_64
[root@vm0 ~]#
The "/usr/include/attr/xattr.h" seems to disappear between
libattr-devel-2.4.47-23.fc28.x86_64 and
libattr-devel-2.4.48-1.fc28.x86_64 . Do you have any idea why this could
happen ?
Regards,
--
Patrice LUCAS
Ingenieur-Chercheur, CEA-DAM/DSSI/SISR/LA2S
tel : +33 (0)1 69 26 47 86
e-mail : patrice.lucas(a)cea.fr