From: kernel test robot <lkp@intel.com>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:dd-diet-rfc 26/30] ld: warning: orphan section `.gnu.linkonce.dyndbg_site' from `arch/x86/kernel/head64.o' being placed in section `.gnu.linkonce.dyndbg_site'
Date: Tue, 25 Oct 2022 22:53:55 +0800 [thread overview]
Message-ID: <202210252248.S5NL82tN-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]
tree: https://github.com/jimc/linux.git dd-diet-rfc
head: 3250797d75caa94f15095d238cb28121a5146f20
commit: 6db1423d5e77269198534c7bf8088269ba4339e7 [26/30] dyndbg: add DEFINE_DYNAMIC_DEBUG_TABLE, use it tacitly RFC
config: x86_64-randconfig-a011 (attached as .config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/jimc/linux/commit/6db1423d5e77269198534c7bf8088269ba4339e7
git remote add jimc https://github.com/jimc/linux.git
git fetch --no-tags jimc dd-diet-rfc
git checkout 6db1423d5e77269198534c7bf8088269ba4339e7
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> ld: warning: orphan section `.gnu.linkonce.dyndbg_site' from `arch/x86/kernel/head64.o' being placed in section `.gnu.linkonce.dyndbg_site'
>> ld: warning: orphan section `.gnu.linkonce.dyndbg' from `arch/x86/kernel/head64.o' being placed in section `.gnu.linkonce.dyndbg'
ld: lib/dynamic_debug.o: in function `dynamic_debug_init':
lib/dynamic_debug.c:1528: undefined reference to `__dyndbg_header'
ld: lib/dynamic_debug.c:1555: undefined reference to `__dyndbg_site_header'
ld: lib/dynamic_debug.c:1555: undefined reference to `__dyndbg_header'
pahole: .tmp_vmlinux.btf: No such file or directory
.btf.vmlinux.bin.o: file not recognized: file format not recognized
--
0-DAY CI Kernel Test Service
https://01.org/lkp
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38846 bytes --]
reply other threads:[~2022-10-25 14:55 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=202210252248.S5NL82tN-lkp@intel.com \
--to=lkp@intel.com \
--cc=jim.cromie@gmail.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 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.