From: kernel test robot <lkp@intel.com>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev,
Kris Van Hees <kris.van.hees@oracle.com>,
Tomas Jedlicka <tomas.jedlicka@oracle.com>,
Alan Maguire <alan.maguire@oracle.com>
Subject: [oracle-dtrace:devel/v2/6.6/dtrace 8/11] ld: warning: CTF linking failed; output will have no CTF section: Type name must not be empty.
Date: Wed, 6 Dec 2023 12:13:12 +0800 [thread overview]
Message-ID: <202312061247.YoLPj5tu-lkp@intel.com> (raw)
tree: https://github.com/oracle/dtrace-linux-kernel devel/v2/6.6/dtrace
head: 03ef4d82312b48741fbdafdd2aaebf3f0567f9a6
commit: f9d9484f2e95b50c63c6e6bd96d727f6d7ab1f3e [8/11] ctf: generate CTF information for the kernel
config: i386-randconfig-141-20231201 (https://download.01.org/0day-ci/archive/20231206/202312061247.YoLPj5tu-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231206/202312061247.YoLPj5tu-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/202312061247.YoLPj5tu-lkp@intel.com/
All warnings (new ones prefixed by >>):
CTF error: fs/smb/client/readdir.c (16): while emitting deduplicated forward, error emitting target type from input type 64
CTF error: deduplicating link type emission failed for (unnamed)
>> ld: warning: CTF linking failed; output will have no CTF section: Type name must not be empty.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-06 4:13 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=202312061247.YoLPj5tu-lkp@intel.com \
--to=lkp@intel.com \
--cc=alan.maguire@oracle.com \
--cc=kris.van.hees@oracle.com \
--cc=nick.alcock@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tomas.jedlicka@oracle.com \
/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.