From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14686] New: genimage.cfg have a hard-coded .ext4 extension which is not compatible with others filesystems's extension
Date: Wed, 23 Mar 2022 12:47:53 +0000 [thread overview]
Message-ID: <bug-14686-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14686
Bug ID: 14686
Summary: genimage.cfg have a hard-coded .ext4 extension which
is not compatible with others filesystems's extension
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: roman@romanlebg.fr
CC: buildroot@uclibc.org
Target Milestone: ---
Created attachment 9251
--> https://bugs.busybox.net/attachment.cgi?id=9251&action=edit
Last portion of the log
Hello, I tried to build an image with a btrfs filesystem for a raspberry pi but
at the end of the make command the genimage script look for a file ending by a
.ext4 extension where it should be a .btrfs in my case. Setting the desired
extension make the build succeed.
Please note that I'm new to the embedded world so I may be missing a
configuration somewhere, you can find the relevant part of the log attached.
Thank you very much.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-03-23 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 12:47 bugzilla [this message]
2022-03-23 19:49 ` [Buildroot] [Bug 14686] genimage.cfg have a hard-coded .ext4 extension which is not compatible with others filesystems's extension bugzilla
2022-03-24 8:32 ` 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-14686-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