From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>, <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 1/2] Revert "Revert "isar-init-build-env: Add /sbin to PATH""
Date: Wed, 16 Mar 2022 06:06:51 +0100 [thread overview]
Message-ID: <66d9329a-66ca-b02b-63b0-7ae248f3afe9@siemens.com> (raw)
In-Reply-To: <20220315184006.2479-2-amikan@ilbers.de>
On 15.03.22 19:40, Anton Mikanovich wrote:
> Image prepare tools like parted and mkfs.vfat from rpi-sdimg bbclass
> can't be found in bullseye chroot because /sbin is not exported into
> PATH by default. Add /sbin manually to fix the issue.
>
> This should be reverted after replaced rpi-sdimg.bbclass by WIC.
>
Why this ping-pong, why not fixing it directly? Raspios limitations?
With Debian, it's a no-brainer to use wic for generating Raspi images,
as done multiple times downstream by now.
Jan
> This reverts commit d0bc682ee81da11f4b939165a4d4383af7ed99de.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> isar-init-build-env | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/isar-init-build-env b/isar-init-build-env
> index 85fb82f..f3d1b6b 100755
> --- a/isar-init-build-env
> +++ b/isar-init-build-env
> @@ -57,4 +57,8 @@ export ISARROOT
> }
> unset ISARROOT
>
> +# wic executes mkdosfs
> +PATH=/sbin:$PATH
> +export PATH
> +
> [ -z "$BUILDDIR" ] || cd "$BUILDDIR"
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-03-16 5:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 18:40 [PATCH v2 0/2] Fix rpi targets build on Bullseye Anton Mikanovich
2022-03-15 18:40 ` [PATCH v2 1/2] Revert "Revert "isar-init-build-env: Add /sbin to PATH"" Anton Mikanovich
2022-03-16 5:06 ` Jan Kiszka [this message]
2022-03-16 5:10 ` Jan Kiszka
2022-03-16 8:41 ` Baurzhan Ismagulov
[not found] ` <3cca4fe9-d13c-2555-ea34-f52eb3d113ee@siemens.com>
2022-03-16 11:19 ` Jan Kiszka
2022-03-15 18:40 ` [PATCH v2 2/2] rpi-sdimg: Limit volume id value Anton Mikanovich
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=66d9329a-66ca-b02b-63b0-7ae248f3afe9@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox