From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: rpi target build fails
Date: Mon, 7 Mar 2022 10:35:49 +0530 [thread overview]
Message-ID: <CALLGG_KQRsnG1yRN_egNVLw9Ybvhm5vg4q5YRCU3KvVT=_OgQg@mail.gmail.com> (raw)
In-Reply-To: <438ab9ca-4eee-36d0-6afe-c2443381637f@ilbers.de>
On Fri, Mar 4, 2022 at 11:15 PM Anton Mikanovich <amikan@ilbers.de> wrote:
>
> 01.03.2022 13:08, vijaikumar....@gmail.com wrote:
>
> Hi,
>
> Currently the rpi target build fails.
>
> There are 2 issues.
> 1. /sbin is not added by default PATH in vanilla debian distributions for normal users. So parted and mkfs cannot be used out of the box.
> 2. mkfs.vfat has a label limit of 11 characters, we are currently passing in the machine name which is longer and errors out as below.
> | Sector size (logical/physical): 512B/512B
> | Partition Table: msdos
> | Disk Flags:
> |
> | Number Start End Size Type File system Flags
> | 1 4194kB 88.1MB 83.9MB primary boot, lba
> | 2 88.1MB 524MB 436MB primary
> |
> | mkfs.vfat: Label can be no longer than 11 characters
> | mkfs.fat 4.2 (2021-01-31)
> | WARNING: exit code 1 from a shell command.
> |
> ERROR: Task (mc:rpi-arm64-v8-bullseye:/home/gomti/vijai_workspace/isar-upstream/isar/meta-isar/recipes-core/images/isar-image-base.bb:do_rpi_sdimg) failed with exit code '1'
>
> I currently donot have any boards to test. So just bringing it to notice here.
>
> For 1 we should probably bring back adding /sbin to path in isar-init-build-env.
>
> Thanks,
> Vijai Kumar K
> --
> You received this message because you are subscribed to the Google Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/5206ee9d-9895-4988-be2e-742c6f3edd10n%40googlegroups.com.
>
>
> Can you give the details of both issues (host distro, environment, Isar commit, target, etc)?
Host: Debian bullseye(11.0)
Commit: 6a54a4212a56070a18b1c9f9ce64eec69357dd48 + some local changes.
target: mc:rpi-arm64-v8-bullseye:isar-image-base
env: PATH is "/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
>
> P.S. I will be out of office next week, will back 2022-03-14
>
>
next prev parent reply other threads:[~2022-03-07 5:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 10:08 vijaikumar....@gmail.com
2022-03-02 8:40 ` Anton Mikanovich
2022-03-04 17:45 ` Anton Mikanovich
2022-03-07 5:05 ` vijai kumar [this message]
2022-03-15 16:13 ` 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='CALLGG_KQRsnG1yRN_egNVLw9Ybvhm5vg4q5YRCU3KvVT=_OgQg@mail.gmail.com' \
--to=vijaikumar.kanagarajan@gmail.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