Skip to contentSkip to conversation

xcompiler

DISCUSSION Mike Shaver 3 participants 4 messages Mar 4, 1998 – Mar 6, 1998 MIPS

lore
Share & tools
lore
#0 lore raw

So, what do I use as an xcompiler (i486->Indy)?
The stuff on linus in ~ftp/pub/crossdev/mips-linux/i486-linux is pretty old-looking, and that scares me a bit.

Mike

#1 lore raw
Quoted 3 lines · Mike Shaver

So, what do I use as an xcompiler (i486->Indy)?
The stuff on linus in ~ftp/pub/crossdev/mips-linux/i486-linux is pretty old-looking, and that scares me a bit.

I think it should still be ok. Most of the changes I made were somehow related to luserland. Anyway, if you're paranoid you can install the binaries of binutils, gcc and libc on your crosscompiler box, then rebuild all the toys. This will save you from the pains of bootstrapping.

Ralf

#2 lore raw

hi,

after mirroring the CVS archive on ftp.linux.sgi.com i tried to crosscompile the kernel (on an irix host, btw). Unfortunately the CVS version seems to be a bit out of date/inconsistent. E.g. fs/nfs/nfsroot.c uses the obsolete struct device ..
I finally managed to compile it with CONFIG_ROOT_NFS by replacing fs/super.c by the one from the main kernel source and changing fs/nfs/nfsroot.c accordingly (just replacing fs/nfs/nfsroot.c won't work) ..

Is anyone going to clean/merge this part of the kernel on sgi.com to be in sync with the main kernel tree??

oliver

#3 lore raw
Quoted 10 lines · Oliver Frommel

after mirroring the CVS archive on ftp.linux.sgi.com i tried to crosscompile the kernel (on an irix host, btw). Unfortunately the CVS version seems to be a bit out of date/inconsistent. E.g. fs/nfs/nfsroot.c uses the obsolete struct device ..
I finally managed to compile it with CONFIG_ROOT_NFS by replacing fs/super.c by the one from the main kernel source and changing fs/nfs/nfsroot.c accordingly (just replacing fs/nfs/nfsroot.c won't work) ..

Is anyone going to clean/merge this part of the kernel on sgi.com to be in sync with the main kernel tree??

The state of the nfsroot stuff is whatever is was when 2.1.73 on which the current CVS kernel is based, was current. I didn't take a closer look if later kernel versions have already fixed that problem, but I hope so.

Ralf