From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [masahiroy:testing5 2/40] <built-in>:1:19: fatal error: 'FORCE' file not found
Date: Wed, 27 Jan 2021 15:18:04 +0800 [thread overview]
Message-ID: <202101271502.8zvFfcsF-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1650 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git testing5
head: 57e1415099ed04c087a8b2e67ec66abc299269a6
commit: 4eedd4e278160da11b984bb2819b45c1b9474ecf [2/40] x86/build: add missing FORCE and fix 'targets' to make if_changed work
config: x86_64-randconfig-a006-20210126 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project 74784a5aa47bb8967e5868831e359fa631abe465)
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
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git/commit/?id=4eedd4e278160da11b984bb2819b45c1b9474ecf
git remote add masahiroy https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
git fetch --no-tags masahiroy testing5
git checkout 4eedd4e278160da11b984bb2819b45c1b9474ecf
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
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 >>):
>> <built-in>:1:19: fatal error: 'FORCE' file not found
#__include_macros "FORCE"
^~~~~~~
1 error generated.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 34727 bytes --]
reply other threads:[~2021-01-27 7:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202101271502.8zvFfcsF-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.