From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libcap: disable gperf
Date: Fri, 31 Mar 2017 16:32:26 +0200 [thread overview]
Message-ID: <20170331143226.GA5555@archie.localdomain> (raw)
In-Reply-To: <20170331133635.3auam5ghmrveomrb@pengutronix.de>
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
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-03-31 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 23:47 Clemens Gruber
2017-03-31 13:36 ` Michael Olbrich
2017-03-31 14:32 ` Clemens Gruber [this message]
2017-03-31 15:15 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170331143226.GA5555@archie.localdomain \
--to=clemens.gruber@pqgruber.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox