From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, leoliu-oc <leoliu-oc@zhaoxin.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 2855/2894] make[5]: *** No rule to make target 'arch/x86/crypto/sm4-zhaoxin-gmi.o', needed by 'arch/x86/crypto/built-in.a'.
Date: Thu, 1 Feb 2024 01:31:29 +0800 [thread overview]
Message-ID: <202402010116.2hQEcT2i-lkp@intel.com> (raw)
Hi leoliu-oc,
First bad commit (maybe != root cause):
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: f6f9abf1a5ef2fc559630c77b3570346dcd19d40
commit: 3b77535a6245966041634eaabc6fe013f20688d8 [2855/2894] Add support for Zhaoxin GMI SM4 Block Cipher algorithm
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240201/202402010116.2hQEcT2i-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240201/202402010116.2hQEcT2i-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202402010116.2hQEcT2i-lkp@intel.com/
All errors (new ones prefixed by >>):
make[5]: *** No rule to make target 'arch/x86/crypto/sm3-zhaoxin-gmi.o', needed by 'arch/x86/crypto/built-in.a'.
>> make[5]: *** No rule to make target 'arch/x86/crypto/sm4-zhaoxin-gmi.o', needed by 'arch/x86/crypto/built-in.a'.
make[5]: Target 'arch/x86/crypto/' not remade because of errors.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-31 17:31 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=202402010116.2hQEcT2i-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=leoliu-oc@zhaoxin.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).