> On Tue, 22 May 2007, firstname.lastname@example.org wrote:
>> scripts/basic/fixdep.c:107:23: error: sys/types.h: No such file or
> You're missing the basic libraries for native compilation.
> | apt-get install libc6-dev
Thanks, I feel like a real idiot. Somehow a bunch of development packages
(libc6-dev, ncurses5-dev, and a few others) got uninstalled on that
Anyway... I was somewhat able to cross-compile a kernel.
Shiva:/usr/src/linux-22.214.171.124# file vmlinux
vmlinux: ELF 64-bit MSB executable, MIPS, MIPS-IV version 1 (SYSV),
statically linked, not stripped
However, when I rsync it over to my O2, it does not boot. It panics almost
immediately, like all other kernels I compiled natively (on the O2) from
something other than the Debian sources. This is the full panic as
displayed from the PROM:
Status register: 0x34010082<CUI,CU0,FR,DE,IPL=8,KX,MODE=KERNEL>
Cause register: 0x8014<CE=0,IP8,EXC=WADE>
Exception PC: 0x801da9fc, Exception RA: 0x8047b0ec
Write address error exception, bad address: 0xfffff000
Saved user regs in hex (&gpda 0x81061838, &_regs 0x81061a38):
arg: 81070000 50000 8049f510 2
tmp: 81070000 a800 804b5808 fff804d9 ffffffff 81412ef4 a13fab68 8
sve: 81070000 c064d6ca 0 46136478 0 c02b80ce 0 be4acb69
t8 81070000 0 t9 0 at 0 v0 c04936d8 v1 0 k1 fffff000
gp 81070000 fp0 sp 0 ra 0
Just to make sure I'm not doing something stupid. Here are the command in
my kernel build sequence:
make CROSS_COMPILE=mips-linux-gnu- oldconfig
make -j 3 CROSS_COMPILE=mips-linux-gnu- all
make CROSS_COMPILE=mips-linux-gnu- INSTALL_MOD_PATH=~/ modules_install
cp vmlinux ~/boot/vmlinux-126.96.36.199
cp System.map ~/boot/System.map-188.8.131.52
cp .config ~/boot/config-184.108.40.206
tar -cf kernel.tar lib boot
CONFIG_CROSSCOMPILE=y in my .config.
I also tried rsyncing the Debian sources over to my Core Duo 2 Debian
machine for cross-compiling. I was unable to get past the .config step.
Debian's patches must hinder cross-compiling in some manner. For example,
make menuconfig seems to refuse to display MIPS as the architecture
I've been mainly using a working Debian 2.6.18 config (i.e. the one from
their package which lets me compile working 2.6.18 from the Debian
sources), but the default config (set to IP32, RK5, etc.) panics at boot
as well. Not sure if the message is 100% identical, I can double check if
anyone thinks that would help.
Thanks again for all the help, it's appreciated.
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
> In personal conversations with technical people, I call myself a hacker.
> when I'm talking to journalists I just say "programmer" or something like
> -- Linus Torvalds