From: kernel test robot <lkp@intel.com>
To: Alexander K <ak@tempesta-tech.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>
Subject: [cel:topic-rpc-with-tls 1/9] net/tls/tls_internal.h:29:10: fatal error: asm/fpu/api.h: No such file or directory
Date: Wed, 8 Dec 2021 08:21:09 +0800 [thread overview]
Message-ID: <202112080816.X2h68yRr-lkp@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux topic-rpc-with-tls
head: 0a17eed0a75672ad449f0b8c8dbe8d67220003f9
commit: 674ca98f07d168e6fbeea6852b81d3536b26d864 [1/9] Port of Tempesta TLS handshakes to the Linux 5.10.68
config: nios2-allyesconfig (https://download.01.org/0day-ci/archive/20211208/202112080816.X2h68yRr-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.2.0
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/cel/linux.git/commit/?id=674ca98f07d168e6fbeea6852b81d3536b26d864
git remote add cel git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux
git fetch --no-tags cel topic-rpc-with-tls
git checkout 674ca98f07d168e6fbeea6852b81d3536b26d864
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nios2 SHELL=/bin/bash
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 >>):
In file included from net/tls/dhm.c:34:
>> net/tls/tls_internal.h:29:10: fatal error: asm/fpu/api.h: No such file or directory
29 | #include <asm/fpu/api.h>
| ^~~~~~~~~~~~~~~
compilation terminated.
--
>> net/tls/ttls.c:28:10: fatal error: asm/fpu/api.h: No such file or directory
28 | #include <asm/fpu/api.h>
| ^~~~~~~~~~~~~~~
compilation terminated.
--
>> net/tls/bignum_x86-64.S:21:10: fatal error: asm/export.h: No such file or directory
21 | #include <asm/export.h>
| ^~~~~~~~~~~~~~
compilation terminated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for CRYPTO_SHA1_SSSE3
Depends on CRYPTO && X86 && 64BIT
Selected by
- TLS_HANDSHAKE && NET && TLS
vim +29 net/tls/tls_internal.h
27
28 #include <linux/types.h>
> 29 #include <asm/fpu/api.h>
30
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-08 0:23 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=202112080816.X2h68yRr-lkp@intel.com \
--to=lkp@intel.com \
--cc=ak@tempesta-tech.com \
--cc=chuck.lever@oracle.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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®