libcap-ng fails with kernel headers 2.6.37

Bug #684969 reported by Matthias Klose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libcap-ng (Ubuntu)
Fix Released
High
Unassigned
linux (Ubuntu)
Invalid
High
Canonical Kernel Team

Bug Description

XATTR_NAME_CAPS isn't defined anymore. Any replacement?

/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I. -I.. -fPIC -DPIC -W -Wall -Wshadow -Wformat -Wundef -D_GNU_SOURCE -g -O2 -MT cap-ng.lo -MD -MP -MF .deps/cap-ng.Tpo -c -o cap-ng.lo cap-ng.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I. -I.. -fPIC -DPIC -W -Wall -Wshadow -Wformat -Wundef -D_GNU_SOURCE -g -O2 -MT cap-ng.lo -MD -MP -MF .deps/cap-ng.Tpo -c cap-ng.c -fPIC -DPIC -o .libs/cap-ng.o
cap-ng.c: In function 'get_bounding_set':
cap-ng.c:225:70: warning: signed and unsigned type in conditional expression
cap-ng.c: In function 'capng_get_caps_fd':
cap-ng.c:325:21: error: 'XATTR_NAME_CAPS' undeclared (first use in this function)
cap-ng.c:325:21: note: each undeclared identifier is reported only once for each function it appears in
cap-ng.c: In function 'capng_apply_caps_fd':
cap-ng.c:539:25: error: 'XATTR_NAME_CAPS' undeclared (first use in this function)
make[2]: *** [cap-ng.lo] Error 1
make[2]: Leaving directory `/scratch/packages/tmp/libcap-ng-0.6.4/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/scratch/packages/tmp/libcap-ng-0.6.4/src'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Related branches

Matthias Klose (doko)
Changed in libcap-ng (Ubuntu):
importance: Undecided → High
milestone: none → natty-alpha-2
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → High
milestone: none → natty-alpha-2
status: New → Confirmed
Matthias Klose (doko)
Changed in linux (Ubuntu):
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
tags: added: kernel-series-unknown
Revision history for this message
Marcin Juszkiewicz (hrw) wrote :

I took 0.6.5 version from upstream and it builds fine - maybe worth updating?

Revision history for this message
Tim Gardner (timg-tpi) wrote :

XATTR_NAME_CAPS did move to another include file, linux/xattr.h

Revision history for this message
Matthias Klose (doko) wrote :

thanks for both comments

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libcap-ng - 0.6.5-0ubuntu1

---------------
libcap-ng (0.6.5-0ubuntu1) natty; urgency=low

  * New upstream version.
    - Reflect changed include file for XATTR_NAME_CAPS. LP: #684969.
  * debian/rules: Fix installation for python2.7.
 -- Matthias Klose <email address hidden> Tue, 14 Dec 2010 19:11:19 +0100

Changed in libcap-ng (Ubuntu):
status: Confirmed → Fix Released
Changed in libcap-ng (Ubuntu):
milestone: natty-alpha-2 → natty-alpha-3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.