[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <201803161439.haTsAZDK%fengguang.wu@intel.com>
Date: Fri, 16 Mar 2018 14:11:19 +0800
From: kbuild test robot <lkp@...el.com>
To: jason.vas.dias@...il.com
Cc: kbuild-all@...org, linux-kernel@...r.kernel.org, x86@...nel.org,
tglx@...utronix.de, mingo@...nel.org, peterz@...radead.org,
andi@...stfloor.org
Subject: Re: [PATCH v4.16-rc5 1/3] x86/vdso: on Intel, VDSO should handle
CLOCK_MONOTONIC_RAW
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v4.16-rc4]
[also build test ERROR on next-20180315]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/jason-vas-dias-gmail-com/x86-vdso-on-Intel-VDSO-should-handle-CLOCK_MONOTONIC_RAW/20180316-070319
config: x86_64-rhel (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
arch/x86/entry/vdso/vclock_gettime.o: In function `__vdso_clock_gettime':
vclock_gettime.c:(.text+0xf7): undefined reference to `__x86_indirect_thunk_rax'
/usr/bin/ld: arch/x86/entry/vdso/vclock_gettime.o: relocation R_X86_64_PC32 against undefined symbol `__x86_indirect_thunk_rax' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
>> collect2: error: ld returned 1 exit status
--
>> arch/x86/entry/vdso/vdso32.so.dbg: undefined symbols found
--
>> objcopy: 'arch/x86/entry/vdso/vdso64.so.dbg': No such file
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Download attachment ".config.gz" of type "application/gzip" (40788 bytes)
Powered by blists - more mailing lists