On Sat, 2015-11-07 at 12:35 +0100, Laurent Vivier wrote: > Le 07/11/2015 00:24, Scott Wood a écrit : > > On Fri, 2015-11-06 at 23:22 +0100, Laurent Vivier wrote: > > > Le 06/11/2015 22:09, Scott Wood a écrit : > > > > On Thu, 2015-11-05 at 12:47 +0100, Laurent Vivier wrote: > > > > > When I try to cross compile a ppc64 kernel, it generally > > > > > fails on the VDSO stage. This is true for powerpc64 cross- > > > > > compiler, but also when I try to build a ppc64le kernel > > > > > on a ppc64 host. > > > > > > > > > > VDSO64L fails: > > > > > > > > > > VDSO64L arch/powerpc/kernel/vdso64/vdso64.so.dbg > > > > > /usr/bin/powerpc64-linux-gnu-ld: > > > > > arch/powerpc/kernel/vdso64/sigtramp.o: > > > > > file class ELFCLASS64 incompatible with ELFCLASS32 > > > > > /usr/bin/powerpc64-linux-gnu-ld: final link failed: File in wrong > > > > > format > > > > > > > > > > This fails because gcc calls "collect2" with > > > > > "--oformat elf32-powerpcle" with ppc64 objects, without the > > > > > "--oformat" ld works well because it use the format of the > > > > > first object as output format. > > > > > > > > > > As this case is correctly managed to build the other kernel > > > > > objects, this patch replaces $(GCC) by $(LD) to generate the > > > > > VDSO objects. > > > > > So at this point, I can: > > > > > > 1- either fix my compiler, > > > 2- or fix the vdso64 linker command. > > > Thank you Scott. With the help of the comment from Segher, I can choose > #1 now :)
What distro/toolchain did you hit this on? I actually wrote this same patch a while back, but from memory it broke in some configurations. So I never merged it. I'll see if I can find my notes and work out exactly why it didn't work, maybe we should merge it anyway, even though the real bug is a toolchain bug. cheers _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev