From: Dominique Martinet <asmadeus@codewreck.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
linux-kernel@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org
Subject: Re: Broken /usr/bin/env (invalid option)
Date: Wed, 9 Dec 2020 14:07:09 +0100 [thread overview]
Message-ID: <20201209130709.GB15469@nautica> (raw)
In-Reply-To: <20201209122437.GA26815@kozik-lap>
Krzysztof Kozlowski wrote on Wed, Dec 09, 2020:
> Your commit ece075366294 ("ld-version: use /usr/bin/env awk for
> shebank") breaks current linux-next on Ubuntu 16.04:
>
> $ make defconfig
>
> make[1]: Entering directory '/mnt/data2/linux/linux-upstream/out'
> GEN Makefile
> *** Default configuration is based on 'multi_v7_defconfig'
> /usr/bin/env: invalid option -- 'S'
> Try '/usr/bin/env --help' for more information.
> init/Kconfig:39: syntax error
> init/Kconfig:38: invalid statement
> ../scripts/kconfig/Makefile:80: recipe for target 'defconfig' failed
> make[2]: *** [defconfig] Error 1
> /mnt/data2/linux/linux-upstream/Makefile:602: recipe for target 'defconfig' failed
> make[1]: *** [defconfig] Error 2
> make[1]: Leaving directory '/mnt/data2/linux/linux-upstream/out'
> Makefile:185: recipe for target '__sub-make' failed
> make: *** [__sub-make] Error 2
>
> https://krzk.eu/#/builders/12/builds/1170/steps/4/logs/stdio
>
> It's not possible to build anything...
Hm, what version of env is that?
I only checked on a couple of systems that env -S exists, but it might
not be available (e.g. now I'm looking, at least busybox env does not
provide -S)
OTOH, we need -S to split arguments because the kernel splits the
shebang as [binary, single argument], so without it awk wouldn't work.
Apparently gawk can work without an explicit -f is invoked as gawk (so
could be used without -S), but that won't be much better wrt
compatibility in my opinion.
I don't see any way to make this work out of the box for me (awk not in
/usr/bin) and you (env not supporting -S), but I guess I can keep that
patch around locally...
Sorry for the trouble.
--
Dominique
next prev parent reply other threads:[~2020-12-09 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 12:24 Broken /usr/bin/env (invalid option) Krzysztof Kozlowski
2020-12-09 13:07 ` Dominique Martinet [this message]
2020-12-09 13:56 ` Krzysztof Kozlowski
2020-12-09 16:20 ` Dominique Martinet
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=20201209130709.GB15469@nautica \
--to=asmadeus@codewreck.org \
--cc=krzk@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
/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