mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Todd <todd@unm.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 50MB kernel on ia64??
Date: Mon, 22 Oct 2001 11:52:54 +1000	[thread overview]
Message-ID: <19244.1003715574@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 21 Oct 2001 19:00:38 CST." <Pine.A41.4.33.0110211857340.119340-200000@aix10.unm.edu>

On Sun, 21 Oct 2001 19:00:38 -0600 (MDT), 
Todd <todd@unm.edu> 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).


  reply	other threads:[~2001-10-22  1:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22  1:00 Todd
2001-10-22  1:52 ` Keith Owens [this message]
2001-10-22  1:14 Matt_Domsch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19244.1003715574@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=todd@unm.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome