folx,
i've recently been trying to compile kernels on ia64 platform. i've
resolved some compiler problems (thanks to help here and from redhat) but
now i've got another problem: kernels built with the attached .config (or
anything even vaguely similar--this one is for 2.4.7) are around 50MB in
size! morevover, there's no vmlinux or bzImage target in the makefile
once ia64 is selected as the architecture. i've been having problems
getting the compiled kernels to boot, but i'm not sure if size is part of
the reason.
is there anything wrong with a kernel that big, or is that what i should
expect on ia64?
thanks,
=========================================================
Todd Underwood, [email protected]
=========================================================
> now i've got another problem: kernels built with the
> attached .config (or
> anything even vaguely similar--this one is for 2.4.7) are
> around 50MB in size!
You've got the gcc -g option specified in the Makefile. 'strip
--strip-debug' your kernel and it'll shrink considerably, or remove the -g.
> morevover, there's no vmlinux or bzImage target in the makefile
> once ia64 is selected as the architecture.
make compressed
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer
Dell Linux Solutions
http://www.dell.com/linux
#2 Linux Server provider with 17% in the US and 14% Worldwide (IDC)!
#3 Unix provider with 18% in the US (Dataquest)!
On Sun, 21 Oct 2001 19:00:38 -0600 (MDT),
Todd <[email protected]> wrote:
>i've recently been trying to compile kernels on ia64 platform. i've
>resolved some compiler problems (thanks to help here and from redhat) but
>now i've got another problem: kernels built with the attached .config (or
>anything even vaguely similar--this one is for 2.4.7) are around 50MB in
>size! morevover, there's no vmlinux or bzImage target in the makefile
>once ia64 is selected as the architecture. i've been having problems
>getting the compiled kernels to boot, but i'm not sure if size is part of
>the reason.
The IA64 patch adds -g to CFLAGS. All the debugging information bloats
vmlinux. For the bootable kernel, I run
strip -g vmlinux -o /boot/efi/vmlinux
You can boot from the unstripped vmlinux, the IA64 loader ignores the
debug data. But the oversized kernels are slower to load and they take
up a lot of space in /boot/efi. Don't understand your compile problem,
make -j4 modules vmlinux
works for me in native IA64 mode (not cross compiling).