Re: Cross-Compile difficulties

[Kumba <kumba@gentoo.org>]

sknauert@wesleyan.edu wrote:
>> On Tue, 22 May 2007, sknauert@wesleyan.edu wrote:
>>> scripts/basic/fixdep.c:107:23: error: sys/types.h: No such file or
>>> directory
>> You're missing the basic libraries for native compilation.
>>
>> | apt-get install libc6-dev
>>
>> Gr{oetje,eeting}s,
>>
>>
> 
> 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
> machine.
> 
> Anyway... I was somewhat able to cross-compile a kernel.
> 
> Shiva:/usr/src/linux-2.6.21.1# 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-2.6.21.1
> cp System.map ~/boot/System.map-2.6.21.1
> cp .config ~/boot/config-2.6.21.1
> cd ~/
> 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
> anymore.
> 
> 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.
> 

One, make sure you're doing "make vmlinux.32", and two, CONFIG_BUILD_ELF64 is 
_not_ enabled.  For 2.6.20, I had to cram in a patch from Frank to get these 
things to not PROM crash (due to the elimination of CPHYSADDY and replacement by 
__pa()), but on 2.6.21, this patch was unnecessary.  Unsure about 2.6.22-rcX.

O2's will boot a pure 64bit kernel, but my experience is that they are 
ridiculously slow at it (the console lags severely).  vmlinux.32 is the modern 
method of 64bit-code-in-a-32bit-shell, which the O2's and IP22 systems will 
swallow much better.

Also, gbefb must be no greater than 4MB memory in menuconfig.

And what's the MHz of your R5000?  300MHz?, if so, it'll be the RM5200, and 
you'll want "RM52xx" for CPU instead.


--Kumba

-- 
Gentoo/MIPS Team Lead

"Such is oft the course of deeds that move the wheels of the world: small hands 
do them because they must, while the eyes of the great are elsewhere."  --Elrond