allmodconfig not working with dummy-tools

allmodconfig not working with dummy-tools

[Michal Suchánek]

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

Re: allmodconfig not working with dummy-tools

[Masahiro Yamada]

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

Re: allmodconfig not working with dummy-tools

[Michal Suchánek]

Hello,

thanks for the fix.

On Fri, Apr 02, 2021 at 01:26:38AM +0900, Masahiro Yamada wrote:
> On Thu, Apr 1, 2021 at 9:39 PM Michal Suchánek <msuchanek@suse.de> wrote:
> 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

Looks like this did not make it to linux-next (0104 does not have it,
0204 does not exist).

Nonetheless, applying the fixup resolves the problem.

Thanks

Michal

Re: allmodconfig not working with dummy-tools

[Michal Suchánek]

On Sat, Apr 03, 2021 at 12:43:02PM +0200, Michal Suchánek wrote:
> Hello,
> 
> thanks for the fix.
> 
> On Fri, Apr 02, 2021 at 01:26:38AM +0900, Masahiro Yamada wrote:
> > On Thu, Apr 1, 2021 at 9:39 PM Michal Suchánek <msuchanek@suse.de> wrote:
> > 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
> 
> Looks like this did not make it to linux-next (0104 does not have it,
> 0204 does not exist).
The fixup still applies locally so it loooks like it is still not
upstream.
> 
> Nonetheless, applying the fixup resolves the problem.
Mostly, I still get:

which: no elfedit in (./scripts/dummy-tools)
> 
> Thanks
> 
> Michal