On Fri, Mar 31, 2017 at 03:36:35PM +0200, Michael Olbrich wrote:
> On Fri, Mar 31, 2017 at 01:47:28AM +0200, Clemens Gruber wrote:
> > Build fails with the most recent gperf 3.1, disable it because it is not
> > essential for libcap.
>
> Hmmm, I'm not sure I like this. using gperf is a runtime performance
> optimization and I'd like to keep that. What goes wrong anyways?
Here is the build log:
arm-v7a-linux-gnueabihf-gcc -O2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-Dlinux -Wall -Wwrite-strings -Wpointer-arith -Wcast-qual -Wcast-align
-Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Winline -Wshadow -g
-fPIC
-I/home/user/project/platform-foo/build-target/libcap-2.25/libcap/../libcap/include/uapi
-I/home/user/project/platform-foo/build-target/libcap-2.25/libcap/../libcap/include
-c cap_file.c -o cap_file.o
In file included from <command-line>:0:0:
./_caps_output.gperf:85:15: error: unknown type name 'size_t'
register size_t n)
^~~~~~
./_caps_output.gperf:108:52: error: unknown type name 'size_t'
__cap_hash_name(register const char *str, register size_t len)
^~~~~~
./_caps_output.gperf:207:21: error: unknown type name 'size_t'
register size_t len)
^~~~~~
./_caps_output.gperf:206:29: error: conflicting types for '__cap_lookup_name'
const struct __cap_token_s *__cap_lookup_name(register const char *str,
^~~~~~~~~~~~~~~~~
./_caps_output.gperf:33:29: note: previous declaration of '__cap_lookup_name'
was here
const struct __cap_token_s *__cap_lookup_name(const char *, unsigned int);
^~~~~~~~~~~~~~~~~
make[2]: *** [Makefile:63: cap_text.o] Error 1
--
I think I found the problem in the Makefile of libcap. Will send a patch
shortly replacing this patch. Then we can leave gperf 3.1 enabled for
libcap.
Clemens
_______________________________________________
ptxdist mailing list
[email protected]