Kernel Cross Compiling
Quoted 2 lines · Herbert Poetzl
[ARCH sparc64/sparc] failed. failed. [ARCH x86_64/x86_64] failed. succeeded.
Your test methology must be broken. 2.4.25rc2 cross compiles just fine here from i386 to x86_64.
-Andi
Quoted 7 lines · Andi Kleen
Quoted 2 lines · Herbert Poetzl
[ARCH sparc64/sparc] failed. failed. [ARCH x86_64/x86_64] failed. succeeded.Your test methology must be broken. 2.4.25rc2 cross compiles just fine here from i386 to
x86_64.
might be, but if, where is it broken ... (if you need any information, let me know)
started a testrun for 2.4.25-rc2 a few minutes ago, and will make the results as well as the detailed build logs available when it completes (takes some time, about 40-60 mins)
TIA,
Herbert
Quoted 1 line
-Andi
Quoted 7 lines · Andi Kleen
Quoted 2 lines · Herbert Poetzl
[ARCH sparc64/sparc] failed. failed. [ARCH x86_64/x86_64] failed. succeeded.Your test methology must be broken. 2.4.25rc2 cross compiles just fine here from i386 to
x86_64.
okay, here is the promised update, a little later as planned, because I discovered that doing 'make dep' would be a great idea too (well that isn't necessary for 2.6.x so it doesn't change those results), but still some archs give troubles ...
linux-2.4.25-rc2 config dep kernel modules
alpha/alpha: OK OK OK OK hppa/parisc: OK OK FAILED FAILED hppa64/parisc: OK OK FAILED FAILED i386/i386: OK OK OK OK m68k/m68k: OK OK OK OK mips/mips: OK OK FAILED FAILED mips64/mips64: OK OK FAILED FAILED ppc/ppc: OK OK OK OK ppc64/ppc64: OK FAILED FAILED OK s390/s390: OK OK OK OK sparc/sparc: OK OK FAILED FAILED sparc64/sparc64: OK OK OK OK x86_64/x86_64: OK OK OK OK
but hey, it's better than before ...
you can get all the details, what and why? it fails from the logs:
http://vserver.13thfloor.at/Stuff/Cross/LOGS-2.4.25-rc2/
any help or hints are appreciated, as it would be great to get this running ...
TIA,
Herbert
Quoted 1 line
-Andi
Quoted 2 lines · Herbert Poetzl
linux-2.4.25-rc2 config dep kernel modules m68k/m68k: OK OK OK OK
Good! :-)
One related question: anyone who knows how to run a cross-depmod, so I can find missing symbol exports without running depmod on the target?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Quoted 5 lines · Geert Uytterhoeven
Quoted 2 lines · Herbert Poetzl
linux-2.4.25-rc2 config dep kernel modules m68k/m68k: OK OK OK OKGood! :-)
yeah but,
2.6.2-rc3 2.6.3-rc2
[ARCH m68k/m68k] failed. failed.
Bad! :(
Quoted 4 lines
One related question: anyone who knows how to run a cross-depmod, so I can find missing symbol exports without running depmod on the target?
../modutils-2.4.26/configure --target=m68k-linux
seems to do something, so it might even work ...
depmod: ELF file /lib/.../kernel/crypto/aes.o not for this architecture
depmod: ELF file /lib/.../kernel/crypto/blowfish.o not for this architecture
HTH,
Herbert
Quoted 9 lines
Gr{oetje,eeting}s,
Geert--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Quoted 11 lines · Herbert Poetzl
Quoted 3 lines · Geert Uytterhoeven
One related question: anyone who knows how to run a cross-depmod, so I can find missing symbol exports without running depmod on the target?
../modutils-2.4.26/configure --target=m68k-linux
seems to do something, so it might even work ...
depmod: ELF file
/lib/.../kernel/crypto/aes.onot for this architecture
depmod: ELF file/lib/.../kernel/crypto/blowfish.onot for this architecture
modutils <= 2.4 was never designed to run in cross compile mode. The modules.dep file created at compile time is a courtesy file, in an attempt to avoid warning messages (no modules.dep) on the very first boot of a new kernel version. Once the kernel has been booted, it ahs its own modules.dep.
Making it run on the target system but handle cross compiled modules pulls in all the problems associated with build and target having different word sizes, different endianess and different object information. modutils 2.4 is now in stable mode, it is only taking bug fixes. A complete rewrite to handle cross compile is not a bug fix.
Bottom line: when building cross compile use make ... DEPMOD=/bin/true to avoid using the local depmod.