From: kernel test robot <lkp@intel.com>
To: Alexander Lobakin <alexandr.lobakin@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [alobakin:kallsyms 3/3] Failed to open ../lib/gcc/or1k-linux/12.1.0/libgcc.syms: No such file or directory at scripts/gen_sympaths.pl line 182.
Date: Fri, 19 Aug 2022 09:45:23 +0800 [thread overview]
Message-ID: <202208190907.vrsbCoX3-lkp@intel.com> (raw)
tree: https://github.com/alobakin/linux kallsyms
head: 0707de5041e9ba702fb490bf92d8742b797c9c3e
commit: 0707de5041e9ba702fb490bf92d8742b797c9c3e [3/3] kallsyms: add option to include relative filepaths into kallsyms
config: openrisc-allmodconfig (https://download.01.org/0day-ci/archive/20220819/202208190907.vrsbCoX3-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 12.1.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/alobakin/linux/commit/0707de5041e9ba702fb490bf92d8742b797c9c3e
git remote add alobakin https://github.com/alobakin/linux
git fetch --no-tags alobakin kallsyms
git checkout 0707de5041e9ba702fb490bf92d8742b797c9c3e
# save the config file
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 ARCH=openrisc
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> Failed to open ../lib/gcc/or1k-linux/12.1.0/libgcc.syms: No such file or directory at scripts/gen_sympaths.pl line 182.
No valid symbol.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-19 1:46 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=202208190907.vrsbCoX3-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandr.lobakin@intel.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