From: Paulo Matos <pmatos@igalia.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem generating rootfs for ci20 defconfig
Date: Mon, 20 Jan 2020 15:45:56 +0100 [thread overview]
Message-ID: <87lfq2mbiz.fsf@igalia.com> (raw)
In-Reply-To: <CAJ4jsafbQ9GBLYd=x95B7QZ=AAd2AdLH-+iuPNnEqhkGfKZ1uw@mail.gmail.com>
Carlos Santos writes:
> On Mon, Jan 20, 2020 at 11:20 AM Paulo Matos <pmatos@igalia.com> wrote:
>>
>> While trying to generate an image using the ci20_defconfig (on
>> git 84d471a0b1) with a few
>> extra libraries added I am getting the following error:
>>
>> >>> Executing post-image script support/scripts/genimage.sh
>> INFO: cmd: "mkdir -p "/home/pmatos/roots/br-root.jsc32-mips/build/genimage.tmp"" (stderr):
>> INFO: cmd: "rm -rf "/home/pmatos/roots/br-root.jsc32-mips/build/genimage.tmp"/*" (stderr):
>> INFO: cmd: "mkdir -p "/home/pmatos/roots/br-root.jsc32-mips/build/genimage.tmp"" (stderr):
>> INFO: cmd: "cp -a "/tmp/tmp.ymKkcnSKic" "/home/pmatos/roots/br-root.jsc32-mips/build/genimage.tmp/root"" (stderr):
>> INFO: cmd: "find '/home/pmatos/roots/br-root.jsc32-mips/build/genimage.tmp/root' -depth -type d -printf '%P\0' | xargs -0 -I {} touch -r '/tmp/tmp.ymKkcnSKic/{}' '/home/pmatos/roots/br-root.jsc32-mips/build/genimage.tmp/root/{}'" (stderr):
>> ERROR: hdimage(sdcard.img): part rootfs size (62914560) too small for rootfs.ext4 (134217728)
>> make[1]: *** [Makefile:808: target-post-image] Error 1
>>
>> Does anybody understand what this part rootfs size refers to? The
>> rootfs.ext4 size if the 128M I set as BR2_TARGET_ROOTFS_EXT2_SIZE but
>> unsure what the other number is, or what it means.
>>
>
> It comes from "size = 60M" in board/ci20/genimage.cfg.
Thanks!
Working now.
--
Paulo Matos
next prev parent reply other threads:[~2020-01-20 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 14:19 [Buildroot] Problem generating rootfs for ci20 defconfig Paulo Matos
2020-01-20 14:33 ` Carlos Santos
2020-01-20 14:45 ` Paulo Matos [this message]
2020-01-20 16:41 ` Carlos Santos
2020-01-20 21:09 ` Arnout Vandecappelle
2020-01-21 21:01 ` Peter Korsgaard
2020-01-21 21:04 ` Peter Korsgaard
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=87lfq2mbiz.fsf@igalia.com \
--to=pmatos@igalia.com \
--cc=buildroot@busybox.net \
/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.