From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/vdso-sparc64-generic-2 12/17] ld.lld: error: arch/sparc/vdso/vclock_gettime.o:(function __vdso_gettimeofday: .text+0x10): unknown relocation (46) against symbol vdso_u_time_data
Date: Fri, 25 Jul 2025 00:30:39 +0800 [thread overview]
Message-ID: <202507250035.UFpeujZm-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/vdso-sparc64-generic-2
head: 208f0c23b4f7408dd631508946283c66a08d7f81
commit: 9f35a7f8ae9b4bb1c4d7dc5e89ab1c617cb149bb [12/17] sparc/vdso: Switch to generic vDSO library
config: sparc64-randconfig-002-20250724 (https://download.01.org/0day-ci/archive/20250725/202507250035.UFpeujZm-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 853c343b45b3e83cc5eeef5a52fc8cc9d8a09252)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250725/202507250035.UFpeujZm-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/202507250035.UFpeujZm-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: arch/sparc/vdso/vclock_gettime.o:(function __vdso_gettimeofday: .text+0x10): unknown relocation (46) against symbol vdso_u_time_data
>> ld.lld: error: arch/sparc/vdso/vclock_gettime.o:(function __vdso_clock_gettime: .text+0x170): unknown relocation (46) against symbol vdso_u_time_data
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-24 16:30 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=202507250035.UFpeujZm-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas.weissschuh@linutronix.de \
/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.