From: "Eilís 'pidge' Ní Fhlannagáin" <pidge@baylibre.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Fix nativesdk-intercepts for chown/chgrp
Date: Thu, 7 Sep 2023 11:38:01 +0000 [thread overview]
Message-ID: <cover.1694086051.git.pidge@baylibre.com> (raw)
This set of patches started out with fixing #15023 where building the sdk with
api-documentation set would fail out. This patch series fixes both of the main
underlying issues.
First, populate_sdk did not the nativesdk chown/chgrp intercepts in $PATH.
The second issue was within the chown/chgrp intercepts which were causing them
to fail badly. I'm not entirely sure these ever worked as prior to my fix the
args for os.execv were:
./scripts/nativesdk-intercept/chown -R pidge:pidge README.md
['root:root', '-R', 'pidge:pidge', 'README.md']
after (which is correct):
./scripts/nativesdk-intercept/chown -R pidge:pidge README.md
['/usr/bin/chown', '-R', 'root:root', 'README.md']
Eilís 'pidge' Ní Fhlannagáin (2):
populate_sdk_base.bbclass: PATH to nativesdk-intercept chown/chgrp
nativesdk-intercept: Fix bad intercept chgrp/chown logic
meta/classes-recipe/populate_sdk_base.bbclass | 1 +
scripts/nativesdk-intercept/chgrp | 5 ++++-
scripts/nativesdk-intercept/chown | 5 ++++-
3 files changed, 9 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2023-09-07 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 11:38 Eilís 'pidge' Ní Fhlannagáin [this message]
2023-09-07 11:38 ` [PATCH 1/2] populate_sdk_base.bbclass: PATH to nativesdk-intercept chown/chgrp Eilís 'pidge' Ní Fhlannagáin
2023-09-07 13:49 ` [OE-core] " Richard Purdie
2023-09-07 11:38 ` [PATCH 2/2] nativesdk-intercept: Fix bad intercept chgrp/chown logic Eilís 'pidge' Ní Fhlannagáin
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=cover.1694086051.git.pidge@baylibre.com \
--to=pidge@baylibre.com \
--cc=openembedded-core@lists.openembedded.org \
/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