From: Jesse Taube <mr.bossman075@gmail.com>
To: buildroot@buildroot.org
Cc: "Raphaël Mélotte" <raphael.melotte@mind.be>,
"Jesse Taube" <Mr.Bossman075@gmail.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Romain Naour" <romain.naour@gmail.com>,
"Jesse Taube" <Mr-Bossman075@gmail.com>
Subject: [Buildroot] [PATCH] package/busybox: Use minimal.config for no MMU
Date: Fri, 18 Aug 2023 22:16:23 -0400 [thread overview]
Message-ID: <20230819021623.3961269-1-Mr.Bossman075@gmail.com> (raw)
When building Busybox for no MMU systems both umask and mask
are not built. During boot-up, they will be called even though they are
not present. This issue is fixed when using busybox-minimal.config
To prevent confusion for future no-mmu boards select minimal.config
for !MMU targets.
Signed-off-by: Jesse Taube <Mr-Bossman075@gmail.com>
---
package/busybox/Config.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/busybox/Config.in b/package/busybox/Config.in
index 5e5c586762..3c2aa515f8 100644
--- a/package/busybox/Config.in
+++ b/package/busybox/Config.in
@@ -13,6 +13,7 @@ if BR2_PACKAGE_BUSYBOX
config BR2_PACKAGE_BUSYBOX_CONFIG
string "BusyBox configuration file to use?"
+ default "package/busybox/busybox-minimal.config" if !BR2_USE_MMU
default "package/busybox/busybox.config"
help
Some people may wish to use their own modified BusyBox
--
2.40.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-08-19 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 2:16 Jesse Taube [this message]
2023-08-21 13:04 ` [Buildroot] [PATCH] package/busybox: Use minimal.config for no MMU Thomas Petazzoni via buildroot
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=20230819021623.3961269-1-Mr.Bossman075@gmail.com \
--to=mr.bossman075@gmail.com \
--cc=Mr-Bossman075@gmail.com \
--cc=buildroot@buildroot.org \
--cc=raphael.melotte@mind.be \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.