[Bugs] [Bug 1218625] New: glfs.h:46:21: fatal error: sys/acl.h: No such file or directory

bugzilla at redhat.com bugzilla at redhat.com
Tue May 5 12:45:06 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1218625

            Bug ID: 1218625
           Summary: glfs.h:46:21: fatal error: sys/acl.h: No such file or
                    directory
           Product: GlusterFS
           Version: mainline
         Component: build
          Keywords: Triaged
          Assignee: bugs at gluster.org
          Reporter: kkeithle at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    ndevos at redhat.com
        Depends On: 1218399, 1218400
            Blocks: 1199352 (glusterfs-3.7.0), 1218359



+++ This bug was initially created as a clone of Bug #1218400 +++

+++ This bug was initially created as a clone of Bug #1218359 +++

Trying to build new libvirt in rawhide, hitting this error with gluster:

In file included from storage/storage_backend_gluster.c:24:0:
/usr/include/glusterfs/api/glfs.h:46:21: fatal error: sys/acl.h: No such file
or directory
compilation terminated.

Doesn't appear to be libvirt specific.

Build: http://koji.fedoraproject.org/koji/taskinfo?taskID=9654514

DEBUG util.py:388:   --> glusterfs-api-devel-3.7.0-0.1.beta1.fc23.x86_64
DEBUG util.py:388:   --> glusterfs-devel-3.7.0-0.1.beta1.fc23.x86_64

--- Additional comment from Niels de Vos on 2015-05-04 21:18:23 CEST ---

glusterfs-api-devel should have a dependency on libacl-devel...


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1199352
[Bug 1199352] GlusterFS 3.7.0 tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1218359
[Bug 1218359] glfs.h:46:21: fatal error: sys/acl.h: No such file or
directory
https://bugzilla.redhat.com/show_bug.cgi?id=1218399
[Bug 1218399] glfs.h:46:21: fatal error: sys/acl.h: No such file or
directory
https://bugzilla.redhat.com/show_bug.cgi?id=1218400
[Bug 1218400] glfs.h:46:21: fatal error: sys/acl.h: No such file or
directory
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list