From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN via buildroot" <buildroot@buildroot.org>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
"Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Subject: Re: [Buildroot] [PATCH 07/18 v3] support/scripts: move merged-usr errors message into check-merged-usr.sh
Date: Thu, 20 Nov 2025 21:52:46 +0100 [thread overview]
Message-ID: <20251120215246.0bed6b94@windsurf> (raw)
In-Reply-To: <34f309044544536e35eb8632020e9ddff0a53553.1756717276.git.yann.morin.1998@free.fr>
Hello Yann,
Sorry, I am late to the party. I haven't followed this whole work, but
this specific patch is causing an issue on my side, see below.
On Mon, 1 Sep 2025 11:01:16 +0200
"Yann E. MORIN via buildroot" <buildroot@buildroot.org> wrote:
> -# The directory to check for merged-usr
> -root="${1}"
> +opts="type:"
> +ARGS="$(getopt -n check-merged -o "" -l "${opts}" -- "${@}")" || exit 1
You're introducing the use of "getopt" here, which is part of
util-linux, and not necessarily installed by default in distributions.
For example the minimal Fedora 42 container that I use for Buildroot
builds now fails to complete a Buildroot build with:
support/scripts/check-merged: line 38: getopt: command not found
make: *** [Makefile:758: target-finalize] Error 1
One option is to check for getopt in support/dependencies and update
the documentation to make installing util-linux a requirement.
However, in several other shell scripts (such as dl-wrapper), we use
getopts which is a bash built-in. For the sake of consistency, it would
probably be better to also use getopts here. Do you think it would be
possible?
Thanks a lot for your feedback!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-11-20 20:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 9:01 [Buildroot] [PATCH 00/18 v3] system: add support for merged-bin (branch yem/merged-bin) Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 01/18 v3] system: reword merged-usr prompt Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 02/18 v3] system: drop superfluous negative condition for default PATH Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 03/18 v3] package/systemd: select merged-usr from package, not init Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 04/18 v3] support/scripts: comonalise checking merged status Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 05/18 v3] support/scripts: prepare for a more complex check for merged directories Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 06/18 v3] support/scripts: also exit in error on improperly merged-usr Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 07/18 v3] support/scripts: move merged-usr errors message into check-merged-usr.sh Yann E. MORIN via buildroot
2025-11-05 10:52 ` Romain Naour via buildroot
2025-11-05 15:59 ` Yann E. MORIN via buildroot
2025-11-05 20:53 ` Romain Naour via buildroot
2025-11-20 20:52 ` Thomas Petazzoni via buildroot [this message]
2025-11-21 13:55 ` Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 08/18 v3] support/scripts: fix and restrict conditions to accept merged dirs Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 09/18 v3] support/scripts: rename check-merged-usr.sh Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 10/18 v3] support/scripts; teach check-merged what to check Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 11/18 v3] system: add support for merged /usr/sbin (aka merged-bin) Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 12/18 v3] support/scripts: reject skeletons or overlays that are unexpectedly merged Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 13/18 v3] package/coreutils: no need for chroot workaround with merged-bin Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 14/18 v3] package/kmod: adjust paths for merged-bin Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 15/18 v3] package/util-linux: " Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 16/18 v3] package/net-tools: no need for ifconfig+route workarounds with merged-bin Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 17/18 v3] toolchain/external: support merged-bin Yann E. MORIN via buildroot
2025-09-01 9:01 ` [Buildroot] [PATCH 18/18 v3] package/systemd: require merged-bin Yann E. MORIN via buildroot
2025-10-11 19:34 ` [Buildroot] [PATCH 00/18 v3] system: add support for merged-bin (branch yem/merged-bin) Yann E. MORIN via buildroot
2025-11-05 22:31 ` Romain Naour 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=20251120215246.0bed6b94@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--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.