From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libcap: disable gperf
Date: Fri, 31 Mar 2017 17:15:58 +0200 [thread overview]
Message-ID: <20170331151558.pngdvq5sgzhioypb@pengutronix.de> (raw)
In-Reply-To: <20170331143226.GA5555@archie.localdomain>
On Fri, Mar 31, 2017 at 04:32:26PM +0200, Clemens Gruber wrote:
> 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:
[...]
> 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.
I'll wait with applying these patches until after the release. I've looked
at the changelog and that looks like it might break other stuff too.
Please keep an eye on it and remind me if I forget to apply this after the
release.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2017-03-31 15:15 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
2017-03-31 15:15 ` Michael Olbrich [this message]
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=20170331151558.pngdvq5sgzhioypb@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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