From: Nathan Chancellor <nathan@kernel.org>
To: Tony Battersby <tonyb@cybernetics.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
Daniel Gomez <da.gomez@samsung.com>,
linux-kbuild@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: remove recent dependency on "truncate" program
Date: Thu, 29 Aug 2024 11:01:06 -0700 [thread overview]
Message-ID: <20240829180106.GA3382912@thelio-3990X> (raw)
In-Reply-To: <d65e598f-4d3e-4092-bc39-16b636181708@cybernetics.com>
On Thu, Aug 29, 2024 at 09:51:25AM -0400, Tony Battersby wrote:
> Remove the recently-added dependency on the truncate program for
> building the kernel. truncate is not available when building the kernel
> under Yocto. It could be added, but it would be better just to avoid
> the unnecessary dependency.
>
> Fixes: 1472464c6248 ("kbuild: avoid scripts/kallsyms parsing /dev/null")
> Signed-off-by: Tony Battersby <tonyb@cybernetics.com>
Seems reasonable to me and appears to generate an identical result for
me.
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> ---
> scripts/link-vmlinux.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
> index 070a319140e8..c27b4e969f20 100755
> --- a/scripts/link-vmlinux.sh
> +++ b/scripts/link-vmlinux.sh
> @@ -215,7 +215,7 @@ kallsymso=
> strip_debug=
>
> if is_enabled CONFIG_KALLSYMS; then
> - truncate -s0 .tmp_vmlinux.kallsyms0.syms
> + true > .tmp_vmlinux.kallsyms0.syms
> kallsyms .tmp_vmlinux.kallsyms0.syms .tmp_vmlinux0.kallsyms
> fi
>
>
> base-commit: 3e9bff3bbe1355805de919f688bef4baefbfd436
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-08-29 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 13:51 [PATCH] kbuild: remove recent dependency on "truncate" program Tony Battersby
2024-08-29 18:01 ` Nathan Chancellor [this message]
2024-09-01 11:43 ` Masahiro Yamada
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=20240829180106.GA3382912@thelio-3990X \
--to=nathan@kernel.org \
--cc=da.gomez@samsung.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=tonyb@cybernetics.com \
/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