From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next 2/2] package/libcap: drop host-libcap dependency
Date: Sat, 8 Jan 2022 23:03:52 +0100 [thread overview]
Message-ID: <20220108230352.17e5d57e@windsurf> (raw)
In-Reply-To: <04eb7314-3beb-c40f-483d-aa142f63a0c6@smile.fr>
On Sat, 8 Jan 2022 21:44:49 +0100
Romain Naour <romain.naour@smile.fr> wrote:
> Hello Fabrice,
>
> Le 30/08/2020 à 12:00, Fabrice Fontaine a écrit :
> > host-libcap was added as a dependency of libcap in commit
> > efae605c88deb15d9c50fd67bdd80f46a78b06c1 without any explanation in the
> > commit message. Drop this dependency that does seem to be needed.
>
> I dont see why host-libcap would be needed to build libcap for the target.
>
> libcap in Yocto doesn't add libcap-native in dependency:
>
> https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-support/libcap/libcap_2.62.bb
>
> This patch needs to be rebased on master since host-gperf has been added rencently.
See https://git.buildroot.org/buildroot/commit/?id=0651b22d638faecb3688f1fd4e0760c31bfba893
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-08 22:04 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 [this message]
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
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=20220108230352.17e5d57e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=romain.naour@smile.fr \
/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.