From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next 1/2] package/libcap: drop host-gperf dependency
Date: Sat, 8 Jan 2022 19:33:07 +0100 [thread overview]
Message-ID: <20220108193307.6db645fa@windsurf> (raw)
In-Reply-To: <20200830100058.4180798-1-fontaine.fabrice@gmail.com>
On Sun, 30 Aug 2020 12:00:57 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> host-gperf dependency was added in commit
> 5d8926add5da1b0bdfb90a41f4d7f857864c5524 without any explanation in the
> commit message but gperf can be disabled through BUILD_GPERF since
> https://git.kernel.org/pub/scm/linux/kernel/git/morgan/libcap.git/commit/?id=3c22870c762f7925b5ff143d76f9affbade275ba
>
> So use this variable and drop this unneeded dependency
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/libcap/libcap.mk | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
So we discussed this with Yann, Peter and Arnout and found that
host-gperf is really quick to build, and provides a better way for
libcap to lookup symbols, thanks to a hash table. So we prefer to keep
things as they are with the host-gperf dependency.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-01-08 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 10:00 [Buildroot] [PATCH/next 1/2] package/libcap: drop host-gperf dependency Fabrice Fontaine
2020-08-30 10:00 ` [Buildroot] [PATCH/next 2/2] package/libcap: drop host-libcap dependency Fabrice Fontaine
2022-01-08 20:44 ` Romain Naour
2022-01-08 22:03 ` Thomas Petazzoni
2022-01-08 20:54 ` Thomas Petazzoni
2020-09-03 20:47 ` [Buildroot] [PATCH/next 1/2] package/libcap: drop host-gperf dependency Thomas Petazzoni
2020-09-05 10:19 ` Fabrice Fontaine
2022-01-08 18:33 ` Thomas Petazzoni [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=20220108193307.6db645fa@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.