Good Morning, On 02/08/2016 06:19 PM, Maciej W. Rozycki wrote: > On Mon, 8 Feb 2016, Daniel Wagner wrote: > >> The generic auxvec.h is used instead the arch specific version. >> This happens when cross compiling the kernel. >> >> mips64-linux-gnu-gcc (GCC) 5.2.1 20151104 (Red Hat Cross 5.2.1-4) >> >> arch/mips/kernel/../../../fs/binfmt_elf.c: In function ‘create_elf_tables’: >> ./arch/mips/include/asm/elf.h:425:14: error: ‘AT_SYSINFO_EHDR’ undeclared (first use in this function) > > There must be something wrong with your setup, or maybe a bug somewhere > in our build machinery you just happened to trigger. Most of us routinely > use a cross-compiler to build the kernel and you're the first one to > report the problem. Yeah, I thought so too and I would also bet on the toolchain. After 'fixing' this small problem I got a nice and shiny binary without any other warnings or errors. > Can you report the compiler invocation that has lead to this error? /usr/bin/mips64-linux-gnu-gcc -Wp,-MD,fs/.binfmt_elf.o.d -nostdinc -isystem /usr/lib/gcc/mips64-linux-gnu/5.2.1/include -I./arch/mips/include -Iarch/mips/include/generated/uapi -Iarch/mips/include/generated -Iinclude -I./arch/mips/include/uapi -Iarch/mips/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -DVMLINUX_LOAD_ADDRESS=0xffffffff88002000 -DDATAOFFSET=0 -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -mno-check-zero-division -mabi=32 -G 0 -mno-abicalls -fno-pic -pipe -msoft-float -DGAS_HAS_SET_HARDFLOAT -Wa,-msoft-float -ffreestanding -march=r5000 -Wa,--trap -I./arch/mips/include/asm/mach-ip22 -I./arch/mips/include/asm/mach-generic -fno-delete-null-pointer-checks -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -fno-var-tracking -assignments -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(binfmt_elf)" -D"KBUILD_MODNAME=KBUILD_STR(binfmt_elf)" -c -o fs/.tmp_binfmt_elf.o fs/binfmt_elf.c > Have you used a default config or a custom one? I used the default one per 'make defconfig ARCH=mips CROSS_COMPILE=/usr/bin/mips64-linux-gnu-' with Fedora 23 MIPS cross toolchain. >> diff --git a/arch/mips/include/asm/auxvec.h b/arch/mips/include/asm/auxvec.h >> new file mode 100644 >> index 0000000..fbd388c >> --- /dev/null >> +++ b/arch/mips/include/asm/auxvec.h >> @@ -0,0 +1 @@ >> +#include <uapi/asm/auxvec.h> > > You're not supposed to require a header in asm/ merely to include a > header of the same name from uapi/asm/ as there are normally > -I./arch/mips/include and -I./arch/mips/include/uapi options present both > at once, in this order, on the compiler's invocation line. So: > > #include <asm/auxvec.h> > > will pull the header from uapi/asm/ if none is present in asm/. Okay, thanks for the explanation. I was pretty confused by the build machinery and saw this include for ARM arch which provides also a their own uapi/asm/auxvec.h Also I looked at the cpp output and saw that there was no uapi/asm/auxvec.h included instead it pulls arch/mips/include/generated/uapi/asm/auxvec.h Not working version: # 1 "arch/mips/include/generated/uapi/asm/auxvec.h" 1 # 1 "./include/uapi/asm-generic/auxvec.h" 1 # 1 "arch/mips/include/generated/uapi/asm/auxvec.h" 2 # 5 "include/uapi/linux/auxvec.h" 2 # 5 "include/linux/auxvec.h" 2 # 12 "./arch/mips/include/asm/elf.h" 2 # 1 "include/linux/fs.h" 1 working version: # 1 "./arch/mips/include/asm/auxvec.h" 1 # 1 "./arch/mips/include/uapi/asm/auxvec.h" 1 # 1 "./arch/mips/include/asm/auxvec.h" 2 # 5 "include/uapi/linux/auxvec.h" 2 # 5 "include/linux/auxvec.h" 2 # 12 "./arch/mips/include/asm/elf.h" 2 # 1 "include/linux/fs.h" 1 I've uploaded the cpp output and the config just in case: https://www.monom.org/data/mips/auxvec/ I am still pretty confused about what should happen in which order. Maybe I should call the Confuse-A-Cat squat team. cheers, daniel
