public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "vijaikumar....@gmail.com" <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: rpi target build fails
Date: Tue, 1 Mar 2022 02:08:37 -0800 (PST)	[thread overview]
Message-ID: <5206ee9d-9895-4988-be2e-742c6f3edd10n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1089 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 1432 bytes --]

             reply	other threads:[~2022-03-01 10:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 10:08 vijaikumar....@gmail.com [this message]
2022-03-02  8:40 ` Anton Mikanovich
2022-03-04 17:45 ` Anton Mikanovich
2022-03-07  5:05   ` vijai kumar
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=5206ee9d-9895-4988-be2e-742c6f3edd10n@googlegroups.com \
    --to=vijaikumar.kanagarajan@gmail.com \
    --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