From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Jose Quaresma <quaresma.jose@gmail.com>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
Jate Sujjavanich <jatedev@gmail.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 2/2] iputils: Use STAGING_DIR_NATIVE for setcap detection
Date: Fri, 19 Feb 2021 11:34:41 +0000 [thread overview]
Message-ID: <617da916aa05ce7cb4c8c0d6367ea02bf1d1ffec.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANPvuRkeiwD0ngL8Ang-v4X2iHUxU9aVK5feDGAQ3kYqST-hdA@mail.gmail.com>
On Fri, 2021-02-19 at 11:26 +0000, Jose Quaresma wrote:
> The only change needed on the recipe are:
>
> -PACKAGECONFIG[libcap] = "-DUSE_CAP=true, -DUSE_CAP=false, libcap"
> +PACKAGECONFIG[libcap] = "-DUSE_CAP=true, -DUSE_CAP=false, libcap libcap-native"
>
> The patch 0001-Add-support-for-setcap-in-STAGING_DIR_NATIVE.patch is not need because
> with the addition of the libcap-native the meson find_program will find the setcap binary on the native
> sysroot and will use it.
Ok, we can take that change.
I'm assuming you still want/need the revert (patch 1/2) as well
though?
That does give us a problem since on systems where libcap
isn't in PACKAGECONFIG, the binaries will be non-deterministic
again.
Cheers,
Richard
next prev parent reply other threads:[~2021-02-19 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 19:21 [PATCH v2 1/2] Revert "iputils: Fix build determinism" Jate Sujjavanich
2021-02-18 19:21 ` [PATCH v2 2/2] iputils: Use STAGING_DIR_NATIVE for setcap detection Jate Sujjavanich
2021-02-18 19:58 ` Alexander Kanavin
2021-02-18 21:44 ` Richard Purdie
2021-02-19 11:26 ` [OE-core] " Jose Quaresma
2021-02-19 11:34 ` Richard Purdie [this message]
2021-02-19 17:37 ` Jate Sujjavanich
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=617da916aa05ce7cb4c8c0d6367ea02bf1d1ffec.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=jatedev@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=quaresma.jose@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.