From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jesse Taube <mr.bossman075@gmail.com>
Cc: "Romain Naour" <romain.naour@gmail.com>,
"Jesse Taube" <Mr-Bossman075@gmail.com>,
"Raphaël Mélotte" <raphael.melotte@mind.be>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/busybox: Use minimal.config for no MMU
Date: Mon, 21 Aug 2023 15:04:00 +0200 [thread overview]
Message-ID: <20230821150400.7f4a1f6c@windsurf> (raw)
In-Reply-To: <20230819021623.3961269-1-Mr.Bossman075@gmail.com>
On Fri, 18 Aug 2023 22:16:23 -0400
Jesse Taube <mr.bossman075@gmail.com> wrote:
> 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(+)
Applied to next with a reworked commit log, see
https://gitlab.com/buildroot.org/buildroot/-/commit/80b56887006cfba50833881dc31f045d494af185
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-21 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 2:16 [Buildroot] [PATCH] package/busybox: Use minimal.config for no MMU Jesse Taube
2023-08-21 13:04 ` Thomas Petazzoni via buildroot [this message]
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=20230821150400.7f4a1f6c@windsurf \
--to=buildroot@buildroot.org \
--cc=Mr-Bossman075@gmail.com \
--cc=mr.bossman075@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox