From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: Error: kernelrelease not valid - run 'make prepare' to update it
Date: Tue, 10 Aug 2021 20:19:28 -0700 [thread overview]
Message-ID: <5ec75ad9-a861-4402-9c16-ae7cb0aaeaba@infradead.org> (raw)
In-Reply-To: <202108111155.RvN9J3Hs-lkp@intel.com>
On 8/10/21 8:16 PM, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 9e723c5380c6e14fb91a8b6950563d040674afdb
> commit: ba64beb17493a4bfec563100c86a462a15926f24 kbuild: check the minimum assembler version in Kconfig
> date: 4 months ago
> config: riscv-randconfig-r025-20210810 (attached as .config)
> compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project d39ebdae674c8efc84ebe8dc32716ec353220530)
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba64beb17493a4bfec563100c86a462a15926f24
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout ba64beb17493a4bfec563100c86a462a15926f24
> # save the attached .config to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross O=build_dir ARCH=riscv prepare
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>>> Error: kernelrelease not valid - run 'make prepare' to update it
> --
> clang --target=riscv64-linux-gnu -no-integrated-as --prefix=riscv64-linux-gnu- -Werror=unknown-warning-option: unknown assembler invoked
> scripts/Kconfig.include:50: Sorry, this assembler is not supported.
> make[3]: *** [scripts/kconfig/Makefile:63: syncconfig] Error 1
> make[2]: *** [Makefile:617: syncconfig] Error 2
> make[1]: *** [Makefile:726: include/config/auto.conf.cmd] Error 2
> make[1]: Failed to remake makefile 'include/config/auto.conf.cmd'.
> make[1]: Failed to remake makefile 'include/config/auto.conf'.
>>> Error: kernelrelease not valid - run 'make prepare' to update it
> make[1]: Target 'prepare' not remade because of errors.
> make: *** [Makefile:215: __sub-make] Error 2
> make: Target 'prepare' not remade because of errors.
Yes, I have noticed this one and a few other ('static') make targets that
should not need a .config file. I have a note to myself to ask about these,
so thanks for bringing it up.
--
~Randy
next prev parent reply other threads:[~2021-08-11 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 3:16 kernel test robot
2021-08-11 3:19 ` Randy Dunlap [this message]
2021-08-13 10:18 ` Masahiro Yamada
2021-08-13 14:52 ` Philip Li
2021-08-13 15:11 ` Randy Dunlap
2021-08-11 3:46 kernel test robot
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=5ec75ad9-a861-4402-9c16-ae7cb0aaeaba@infradead.org \
--to=rdunlap@infradead.org \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=nathan@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
all inboxes | Powered by JetHome®