Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Masahiro Yamada <masahiroy@kernel.org>,
	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
Subject: Re: kbuild: mksysmap: Build regression for next-20240604
Date: Wed, 5 Jun 2024 17:14:42 +0100	[thread overview]
Message-ID: <365d7243-812c-4d65-b91b-a9843f038319@nvidia.com> (raw)
In-Reply-To: <CAK7LNAR5fYTzJLtRDSob2TuL0Lt0bxCayY8sx0_1+UEuu1Hz9A@mail.gmail.com>


On 05/06/2024 14:02, Masahiro Yamada wrote:
> On Wed, Jun 5, 2024 at 9:56 PM Kent Overstreet
> <kent.overstreet@linux.dev> wrote:
>>
>> On Wed, Jun 05, 2024 at 09:14:23AM +0100, Jon Hunter wrote:
>>> 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
>>
>> I'll drop it, but we need a real fix then, my CI builders are broken
>> without it...

Proper fixes are always good so that everyone's CI builders work :-)

> I will apply Richard's patch instead and send a pull request for -rc3.
> 
> https://lore.kernel.org/linux-kbuild/CAK7LNASx_iSWZ14W5dpTOM87kB8A-Paq8fM_3nKH5tdfJQ7+ZQ@mail.gmail.com/T/#mfa8b89c64a6a14a764338e9398d40be9bc48cdf1

Works for me!

Thanks
Jon

-- 
nvpublic

      reply	other threads:[~2024-06-05 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  8:14 kbuild: mksysmap: Build regression for next-20240604 Jon Hunter
2024-06-05 12:56 ` Kent Overstreet
2024-06-05 13:02   ` Masahiro Yamada
2024-06-05 16:14     ` Jon Hunter [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=365d7243-812c-4d65-b91b-a9843f038319@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