2.4.21-pre5 kksymoops for i386/ia64
Quoted 5 lines · Keith Owens
Automatic decoding of oops on 2.5 has been very useful, so this patch adds kksymoops support to 2.4.21-pre5. Currently only for i386 and ia64, other architectures are easy to add.
+KALLSYMS =
/sbin/kallsyms
Kallsyms is arch-specific, isn't it? So shouldn't that be $(CROSS_COMPILE)kallsyms?
How does one go about making non-native kallsyms?
The 2.5 kallsyms doesn't break cross-compilation, does it?
Signature · 1 line
dwmw2
Quoted 9 lines · David Woodhouse
Quoted 5 lines · Keith Owens
Automatic decoding of oops on 2.5 has been very useful, so this patch adds kksymoops support to 2.4.21-pre5. Currently only for i386 and ia64, other architectures are easy to add.
+KALLSYMS =
/sbin/kallsymsKallsyms is arch-specific, isn't it? So shouldn't that be $(CROSS_COMPILE)kallsyms?
kallsyms does not build in cross compile mode. There are hacked up versions of kallsyms for specific cross compile environments and the user selects them by make KALLSYMS=... I was going to make modutils fully cross compile compatible but now it has moved into the kernel there is no point. Pity that the kernel version is incomplete.
Quoted 1 line
How does one go about making non-native kallsyms?
Google for kallsyms i386 ia64.
Quoted 1 line
The 2.5 kallsyms doesn't break cross-compilation, does it?
No, but neither does it support the section data that is needed for kdb (and possibly kgdb). The removal of section data in 2.5 is one of the reasons that I no longer do kdb patches for 2.5 kernels. If you want to destroy kdb for 2.4 kernels as well, go ahead and use the 2.5 kallsyms. It will actually make my life easier if I no longer have to support kdb on standard kernels.
This patch does not break cross compilation either. It is a restriction that you cannot use kallsyms in cross compile mode unless you have a version like kallsyms_i386_ia64.