From: Dragan Simic <dsimic@manjaro.org>
To: "Leon M. Busch-George" <leon@georgemail.de>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH] Makefile: use shell to calculate map_size
Date: Sat, 02 Mar 2024 22:13:08 +0100 [thread overview]
Message-ID: <f27f49c04e7c4dca0112003e44bd9814@manjaro.org> (raw)
In-Reply-To: <20240302131728.148251-1-leon@georgemail.de>
Hello Leon,
On 2024-03-02 14:17, Leon M. Busch-George wrote:
> From: "Leon M. Busch-George" <leon@georgemail.eu>
>
> The error message "bc: command not found" is easily missed since the
> build continues.
> bc is not a part of coreutils or base-devel. POSIX sh can also do the
> calculation.
>
> Signed-off-by: Leon M. Busch-George <leon@georgemail.eu>
Please, see a nitpick below. Otherwise, the patch is looking
good to me.
Reviewed-by: Dragan Simic <dsimic@manjaro.org>
> ---
> Makefile | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 7a3209bd9e..41dc4baad2 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1275,9 +1275,9 @@ OBJCOPYFLAGS_u-boot-nodtb.bin := -O binary \
> binary_size_check: u-boot-nodtb.bin FORCE
> @file_size=$(shell wc -c u-boot-nodtb.bin | awk '{print $$1}') ; \
> map_size=$(shell cat u-boot.map | \
> - awk '/_image_copy_start/ {start = $$1} /_image_binary_end/ {end =
> $$1} END {if (start != "" && end != "") print "ibase=16; "
> toupper(end) " - " toupper(start)}' \
> + awk '/_image_copy_start/ {start = $$1} /_image_binary_end/ {end =
> $$1} END {if (start != "" && end != "") print "echo $$((0x"
> toupper(end) " - 0x" toupper(start) "))"}' \
> | sed 's/0X//g' \
> - | bc); \
> + | sh); \
Maybe "sh -s" could be used instead, just for some additional
strictness.
> if [ "" != "$$map_size" ]; then \
> if test $$map_size -ne $$file_size; then \
> echo "u-boot.map shows a binary size of $$map_size" >&2 ; \
next prev parent reply other threads:[~2024-03-02 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 13:17 [PATCH] Makefile: use shell to calculate map_size Leon M. Busch-George
2024-03-02 21:13 ` Dragan Simic [this message]
[not found] ` <20240304154007.67df1822@couch-potassium>
2024-03-04 15:57 ` Leon Busch-George
2024-03-04 20:38 ` [PATCH v2] " Leon M. Busch-George
2024-03-05 16:40 ` Leon Busch-George
2024-03-05 16:46 ` [PATCH v3] " Leon M. Busch-George
[not found] ` <343281d5cf78e8c473e40f58361e01e1@manjaro.org>
2024-03-10 10:33 ` Dragan Simic
[not found] ` <b594973ddce475d2a2baead6f4028134@manjaro.org>
2024-03-10 10:12 ` [PATCH v2] " Dragan Simic
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=f27f49c04e7c4dca0112003e44bd9814@manjaro.org \
--to=dsimic@manjaro.org \
--cc=leon@georgemail.de \
--cc=u-boot@lists.denx.de \
/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