From: Masahiro Yamada <masahiroy@kernel.org>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Philipp Rudo <prudo@linux.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: allmodconfig not working with dummy-tools
Date: Fri, 2 Apr 2021 01:26:38 +0900 [thread overview]
Message-ID: <CAK7LNAQwi=Nd+OfHrXBMJtC=f262K+=XFqeYBUz=Qx2Bjbg+yg@mail.gmail.com> (raw)
In-Reply-To: <20210401123944.GJ15381@kitsune.suse.cz>
On Thu, Apr 1, 2021 at 9:39 PM Michal Suchánek <msuchanek@suse.de> wrote:
>
> Hello,
>
> running allmodconfig with dumy-tools I get:
>
> which: no elfedit in (./scripts/dummy-tools)
> scripts/dummy-tools/gcc: unknown assembler invoked
> scripts/Kconfig.include:50: Sorry, this assembler is not supported.
> scripts/kconfig/Makefile:77: recipe for target 'allmodconfig' failed
> make[1]: *** [allmodconfig] Error 1
> Makefile:648: recipe for target 'allmodconfig' failed
> make: *** [allmodconfig] Error 2
>
> I use allmodconfig to enable any unknown options on new kernel version
> automaticallly so it can be build-tested.
>
> Can this be fixed or is there some other way of automatically udating
> the config after new options are added?
>
> Thanks
>
> Michal
Thanks for the report.
I squashed the following. Please wait for tomorrow's linux-next.
diff --git a/scripts/dummy-tools/gcc b/scripts/dummy-tools/gcc
index 39e65fee59bd..f6d543725f1e 100755
--- a/scripts/dummy-tools/gcc
+++ b/scripts/dummy-tools/gcc
@@ -67,6 +67,12 @@ if arg_contain -E "$@"; then
fi
fi
+# To set CONFIG_AS_IS_GNU
+if arg_contain -Wa,--version "$@"; then
+ echo "GNU assembler (scripts/dummy-tools) 2.50"
+ exit 0
+fi
+
if arg_contain -S "$@"; then
# For scripts/gcc-x86-*-has-stack-protector.sh
if arg_contain -fstack-protector "$@"; then
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2021-04-01 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 12:39 allmodconfig not working with dummy-tools Michal Suchánek
2021-04-01 16:26 ` Masahiro Yamada [this message]
2021-04-03 10:43 ` Michal Suchánek
2021-04-08 10:11 ` Michal Suchánek
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='CAK7LNAQwi=Nd+OfHrXBMJtC=f262K+=XFqeYBUz=Qx2Bjbg+yg@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msuchanek@suse.de \
--cc=prudo@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.