From: Jon Hunter <jonathanh@nvidia.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
linux-kbuild@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>
Subject: kbuild: mksysmap: Build regression for next-20240604
Date: Wed, 5 Jun 2024 09:14:23 +0100 [thread overview]
Message-ID: <21cdf8ef-e2fe-4247-9390-4b3d975f80a3@nvidia.com> (raw)
Hi Kent,
Since next-20240604 I noticed a build regression in our farm builders
and I am seeing the following error ...
/usr/bin/env: invalid option -- 'S'
Try '/usr/bin/env --help' for more information.
These builders have an older version of 'env' that do not support the
'-S' argument and so your change [0] is breaking the for these
machines. I did not see your patch on any list and found it on your
bcachefs tree [1]. So not clear if this has been reviewed and if this
is trying to fix some related to Masahiro change [2]?
It is also not clear what the minimum version of 'env' is supported
for building the linux kernel, but these builders have been building
the kernel fine for years.
Thanks
Jon
[0] https://evilpiepirate.org/git/bcachefs.git/commit/?h=for-next&id=973eca8db5570dd0c3f2b3190867138cc446eb3b
[1] https://evilpiepirate.org/git/bcachefs.git/log/?h=for-next
[2] https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git/commit/?h=kbuild&id=b18b047002b7d3b19d9fb905c1bd2a214016c153
next reply other threads:[~2024-06-05 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 8:14 Jon Hunter [this message]
2024-06-05 12:56 ` kbuild: mksysmap: Build regression for next-20240604 Kent Overstreet
2024-06-05 13:02 ` Masahiro Yamada
2024-06-05 16:14 ` Jon Hunter
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=21cdf8ef-e2fe-4247-9390-4b3d975f80a3@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=masahiroy@kernel.org \
/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