public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Kernel: which machine to choose?
Date: Tue, 08 Aug 2000 19:10:21 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205282@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205272@msgid-missing>

	I get 40 MB kernels, although the size of text/data/bss/etc. are about the
	same as the 7-8 MB kernels shipped with the RedHat distro on my machine.

Strip out the debug info if you don't want it.  That accounts for most of
the extra size.  There are people working on fixing the dwarf2 debug info
size problem, but I don't know when the result will be available or how well
it will work.

	And, trying to get the newer compiler to work on the RedHat distro has
	been a little problematic.

Which "new" compiler are you trying to use?  000216-final is the latest
compiler release that we have made.  If you try to use something from the
FSF (e.g. gcc.gnu.org), you are likely to run into lots of problem.
We will be making a new compiler release soon, in conjunction with the
glibc 2.2 release that Jes Sorensen is working on.  You might want to wait
for that.

Jim


  parent reply	other threads:[~2000-08-08 19:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-08  7:14 [Linux-ia64] Kernel: which machine to choose? G\351raud Krawezik
2000-08-08 16:02 ` Broadfoot, KenX
2000-08-08 17:16 ` David Mosberger
2000-08-08 18:26 ` Uros Prestor
2000-08-08 18:51 ` David Mosberger
2000-08-08 18:55 ` Gerrit.Huizenga
2000-08-08 18:55 ` Jes Sorensen
2000-08-08 19:10 ` Jim Wilson [this message]
2000-08-08 19:15 ` Don Dugger
2000-08-08 19:36 ` Jes Sorensen
2000-08-08 19:43 ` Uros Prestor
2000-08-09 10:36 ` Gerrit.Huizenga
2000-08-09 16:37 ` Broadfoot, KenX

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=marc-linux-ia64-105590678205282@msgid-missing \
    --to=wilson@cygnus.com \
    --cc=linux-ia64@vger.kernel.org \
    /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