RE: [cobalt-developers] Compilation Question.

[BSmith@xxxxxxxxxxx]

Tim,

Thanks .. believe it or not, I actually tried to find info on building
Kernels on Cobalt's.  I guess I just have been looking in the wrong places.

~Brian

-----Original Message-----
From: Tim Hockin [mailto:thockin@xxxxxxx]
Sent: Thursday, February 21, 2002 1:52 PM
To: cobalt-developers@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-developers] Compilation Question.


BSmith@xxxxxxxxxxx wrote:

> make oldconfig
> make menuconfig *** to change what I want to compile into the kernel

gratuitous - no need for the oldconfig

> make dep
> make modules
> make modules_install

you forgot clean after dep.  'make dep clean'.  You also forgot to actually
make a kernel.  'make cobalt' if you use our source, 'make vmlinux; gzip
vmlinux' if you don't.

make <somethingconfig>
make dep clean cobalt modules
make cobalt-install
 
> I go into /usr/src/linux/arch/i386/boot directory
> but there is not zImage there :-(
> I look in the /usr/src/linux directory, there is a vmlinux file.
> So, I put it into my /boot directory
> but, I do NOT know where to tell it what file to boot off of.

Ok, firstly, you didn't make a kernel, you made modules.  Secondly, you
haven't read anything written about building kernels on Cobalt systems.  We
don't use zImage.  In fact, 'make zImage' will fail.  'make cobalt' or
'make vmlinux; gzip vmlinux' is what you want.  When 'make cobalt' is done,
you'll have vmlinux.[gz,bz2] files.  Copy THOSE to /boot.  Or just use
'make cobalt-install'.

Tim
-- 
Tim Hockin
Systems Software Engineer
Sun Microsystems, Cobalt Server Appliances
thockin@xxxxxxx

_______________________________________________
cobalt-developers mailing list
cobalt-developers@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-developers