[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNASLc=ik9QdX4K_XuN=cg+1VcUBk-y5EnQEtOG+qOWaY=Q@mail.gmail.com>
Date: Wed, 11 Sep 2024 18:38:19 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Kris Van Hees <kris.van.hees@...cle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the kbuild tree
On Wed, Sep 11, 2024 at 9:18 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> make[3]: *** Deleting file 'modules.builtin.ranges'
> /bin/sh: 1: scripts/generate_builtin_ranges.awk: not found
> make[3]: *** [scripts/Makefile.vmlinux:47: modules.builtin.ranges] Error 127
> make[2]: *** [Makefile:1157: vmlinux] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [Makefile:224: __sub-make] Error 2
> make: *** [Makefile:224: __sub-make] Error 2
> Command exited with non-zero status 2
>
> Caused by commit
>
> 04b15cdd611a ("kbuild: generate offset range data for builtin modules")
>
> I do not have gawk installed - I do have mawk installed (as awk). Does
> this script actually need gawk, or will just plain awk suffice?
>
> I have installed gawk.
>
This is what I was worried about.
As Documentation/process/changes.rst was modified in that commit,
it specifically requires GNU AWK.
Anyway, you were able to fix the build error
by installing /usr/bin/gawk.
If a distro installs gawk somewhere else,
(/usr/local/bin/gawk, for example), it is a problem.
The shebang "#!/usr/bin/gawk -f" will not work.
"#!/usr/bin/env gawk -f" will not work either.
More people may start complaining about it.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists