2
0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-28 07:04:00 +08:00
linux-next/arch/riscv/kernel/vdso
Palmer Dabbelt 4938c79bd0
RISC-V: Use KBUILD_CFLAGS instead of KCFLAGS when building the vDSO
If you use a 64-bit compiler to build a 32-bit kernel then you'll get an
error when building the vDSO due to a library mismatch.  The happens
because the relevant "-march" argument isn't supplied to the GCC run
that generates one of the vDSO intermediate files.

I'm not actually sure what the right thing to do here is as I'm not
particularly familiar with the kernel build system.  I poked the
documentation and it appears that KCFLAGS is the correct thing to do
(it's suggested that should be used when building modules), but we set
KBUILD_CFLAGS in arch/riscv/Makefile.

This does at least fix the build error.

Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
2018-08-13 08:31:28 -07:00
..
.gitignore RISC-V: User-facing API 2017-09-26 15:26:48 -07:00
clock_getres.S RISC-V: Add VDSO entries for clock_get/gettimeofday/getcpu 2017-11-27 07:51:39 -08:00
clock_gettime.S RISC-V: Add VDSO entries for clock_get/gettimeofday/getcpu 2017-11-27 07:51:39 -08:00
flush_icache.S RISC-V: Make __NR_riscv_flush_icache visible to userspace 2018-01-07 15:14:37 -08:00
getcpu.S RISC-V: Add VDSO entries for clock_get/gettimeofday/getcpu 2017-11-27 07:51:39 -08:00
gettimeofday.S RISC-V: Add VDSO entries for clock_get/gettimeofday/getcpu 2017-11-27 07:51:39 -08:00
Makefile RISC-V: Use KBUILD_CFLAGS instead of KCFLAGS when building the vDSO 2018-08-13 08:31:28 -07:00
rt_sigreturn.S RISC-V: User-facing API 2017-09-26 15:26:48 -07:00
vdso.lds.S RISC-V: Allow userspace to flush the instruction cache 2017-11-30 12:58:29 -08:00
vdso.S RISC-V: User-facing API 2017-09-26 15:26:48 -07:00