Messages in this thread |  | | Date | Fri, 14 Feb 2014 14:32:51 -0800 | From | "H. Peter Anvin" <> | Subject | Re: [PATCH v16 0/10] Add 32 bit VDSO time function support |
| |
I still get build errors.
i386 allyesconfig, i386 allmodconfig as well as a more basic i386 configuration:
arch/x86/vdso/vdso32-int80.so.dbg: undefined symbols found make[4]: *** [arch/x86/vdso/vdso32-int80.so.dbg] Error 1
x86-64 allyesconfig and x86-64 allmodconfig:
/home/hpa/kernel/distwork/arch/x86/vdso/vdso32/../vclock_gettime.c:128:4: warning: symbol 'hpet_page' was not declared . Should it be static? /home/hpa/kernel/distwork/arch/x86/vdso/vdso32/../vclock_gettime.c:134:33: warning: incorrect type in argument 1 (diff erent address spaces) /home/hpa/kernel/distwork/arch/x86/vdso/vdso32/../vclock_gettime.c:134:33: expected void const volatile [noderef] < asn:2>*addr /home/hpa/kernel/distwork/arch/x86/vdso/vdso32/../vclock_gettime.c:134:33: got unsigned char [toplevel] * /home/hpa/kernel/distwork/arch/x86/vdso/vdso32/../vclock_gettime.c:294:13: warning: symbol '__vdso_clock_gettime' was not declared. Should it be static? /home/hpa/kernel/distwork/arch/x86/vdso/vdso32/../vclock_gettime.c:322:13: warning: symbol '__vdso_gettimeofday' was n ot declared. Should it be static? /home/hpa/kernel/distwork/arch/x86/vdso/vdso32/../vclock_gettime.c:343:16: warning: symbol '__vdso_time' was not decla red. Should it be static? CC arch/x86/vdso/vdso32/vclock_gettime.o /home/hpa/kernel/distwork/arch/x86/vdso/vdso32/vclock_gettime.c:1:0: sorry, unimplemented: -mfentry isn’t supported fo r 32-bit in combination with -fpic #define BUILD_VDSO32 ^ make[4]: *** [arch/x86/vdso/vdso32/vclock_gettime.o] Error 1 make[3]: *** [arch/x86/vdso] Error 2 make[3]: *** Waiting for unfinished jobs....
This is after I removed the incorrect "generated/" filename prefix in patch 9.
-hpa
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |