From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14196] New: when using raspberrypicm4io_64_defconfig, make fails with mkfs.ext4: No such file or directory while trying to determine filesystem size
Date: Sun, 05 Sep 2021 11:16:01 +0000 [thread overview]
Message-ID: <bug-14196-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14196
Bug ID: 14196
Summary: when using raspberrypicm4io_64_defconfig, make fails
with mkfs.ext4: No such file or directory while trying
to determine filesystem size
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: leon@exquisip.nl
CC: buildroot@uclibc.org
Target Milestone: ---
Created attachment 9086
--> https://bugs.busybox.net/attachment.cgi?id=9086&action=edit
patch fs/ext2/ext2.mk to touch file that'll contain filesystem
After using raspberrypicm4io_64_defconfig, then doing make, the build process
ends as follows:
...
printf ' \n' >>
/home/ldr/src/buildroot/output/build/buildroot-fs/ext2/fakeroot
printf ' \n' >>
/home/ldr/src/buildroot/output/build/buildroot-fs/ext2/fakeroot
printf ' rm -f /home/ldr/src/buildroot/output/images/rootfs.ext2\n
/home/ldr/src/buildroot/output/host/sbin/mkfs.ext4 -d
/home/ldr/src/buildroot/output/build/buildroot-fs/ext2/target -r 1 -N 0 -m 5 -L
"rootfs" -O ^64bit /home/ldr/src/buildroot/output/images/rootfs.ext2 "120M" ||
{ ret=$?; echo "*** Maybe you need to increase the filesystem size
(BR2_TARGET_ROOTFS_EXT2_SIZE)" 1>&2; exit $ret; }\n' >>
/home/ldr/src/buildroot/output/build/buildroot-fs/ext2/fakeroot
chmod a+x /home/ldr/src/buildroot/output/build/buildroot-fs/ext2/fakeroot
PATH="/home/ldr/src/buildroot/output/host/bin:/home/ldr/src/buildroot/output/host/sbin:/home/ldr/.asdf/shims:/opt/asdf-vm/bin:/usr/local/bin:/usr/bin:/var/lib/snapd/snap/bin:/usr/local/sbin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl"
FAKEROOTDONTTRYCHOWN=1 /home/ldr/src/buildroot/output/host/bin/fakeroot --
/home/ldr/src/buildroot/output/build/buildroot-fs/ext2/fakeroot
rootdir=/home/ldr/src/buildroot/output/build/buildroot-fs/ext2/target
table='/home/ldr/src/buildroot/output/build/buildroot-fs/full_devices_table.txt'
mke2fs 1.46.3 (27-Jul-2021)
mkfs.ext4: No such file or directory while trying to determine filesystem size
*** Maybe you need to increase the filesystem size
(BR2_TARGET_ROOTFS_EXT2_SIZE)
make: *** [fs/ext2/ext2.mk:63:
/home/ldr/src/buildroot/output/images/rootfs.ext2] Error 1
--
I can reproduce in commandline by just running:
/home/ldr/src/buildroot/output/host/sbin/mkfs.ext4 -d
/home/ldr/src/buildroot/output/build/buildroot-fs/ext2/target -r 1 -N 0 -m 5 -L
"rootfs" -O ^64bit /home/ldr/src/buildroot/output/images/rootfs.ext2 "120M"
--
so the mkfs.ext4 wants the file that will contain the filesystem to already
exist, which it doesnt, becuase it's removed one command earlier.
--
I was able to fix my issue by adding a touch in fs/ext2/ext2.mk.
Please see attachment.
But not sure if this is a correct way to fix my issue.
Hope it helps.
Thanks,
Leon
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-09-05 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 11:16 bugzilla [this message]
2021-09-05 14:39 ` [Buildroot] [Bug 14196] when using raspberrypicm4io_64_defconfig, make fails with mkfs.ext4: No such file or directory while trying to determine filesystem size bugzilla
2021-09-05 16:46 ` bugzilla
2021-09-05 18:42 ` bugzilla
2021-09-11 10:04 ` bugzilla
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=bug-14196-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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