From: kernel test robot <lkp@intel.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jcmvbkbc-xtensa:xtensa-5.14-call0 5/10] xtensa-linux-gcc: error: unrecognized command-line option '-mabi=call0'
Date: Fri, 6 Aug 2021 19:38:01 +0800 [thread overview]
Message-ID: <202108061952.3eg9gTTC-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2804 bytes --]
tree: https://github.com/jcmvbkbc/linux-xtensa xtensa-5.14-call0
head: c929fa543ba83fa34c6f411ea26f0fc78304f960
commit: dfb68769c2d4422b2c3acfad47788cd26a8f2086 [5/10] WIP: xtensa: add call0 kernel ABI support
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 10.3.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://github.com/jcmvbkbc/linux-xtensa/commit/dfb68769c2d4422b2c3acfad47788cd26a8f2086
git remote add jcmvbkbc-xtensa https://github.com/jcmvbkbc/linux-xtensa
git fetch --no-tags jcmvbkbc-xtensa xtensa-5.14-call0
git checkout dfb68769c2d4422b2c3acfad47788cd26a8f2086
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross O=build_dir ARCH=xtensa 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 >>):
>> xtensa-linux-gcc: error: unrecognized command-line option '-mabi=call0'
--
>> xtensa-linux-gcc: error: unrecognized command-line option '-mabi=call0'
>> xtensa-linux-gcc: error: unrecognized command-line option '-mabi=call0'
make[2]: *** [scripts/Makefile.build:272: scripts/mod/empty.o] Error 1
>> xtensa-linux-gcc: error: unrecognized command-line option '-mabi=call0'
make[2]: *** [scripts/Makefile.build:117: scripts/mod/devicetable-offsets.s] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [Makefile:1234: prepare0] Error 2
make[1]: Target 'modules_prepare' not remade because of errors.
make: *** [Makefile:215: __sub-make] Error 2
make: Target 'modules_prepare' not remade because of errors.
--
>> xtensa-linux-gcc: error: unrecognized command-line option '-mabi=call0'
scripts/genksyms/parse.y: warning: 9 shift/reduce conflicts [-Wconflicts-sr]
scripts/genksyms/parse.y: warning: 5 reduce/reduce conflicts [-Wconflicts-rr]
>> xtensa-linux-gcc: error: unrecognized command-line option '-mabi=call0'
make[2]: *** [scripts/Makefile.build:272: scripts/mod/empty.o] Error 1
>> xtensa-linux-gcc: error: unrecognized command-line option '-mabi=call0'
make[2]: *** [scripts/Makefile.build:117: scripts/mod/devicetable-offsets.s] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [Makefile:1234: prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:215: __sub-make] Error 2
make: Target 'prepare' not remade because of errors.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 67854 bytes --]
reply other threads:[~2021-08-06 11:38 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=202108061952.3eg9gTTC-lkp@intel.com \
--to=lkp@intel.com \
--cc=jcmvbkbc@gmail.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