mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: "umesh@websurfer.com.np" <umesh@websurfer.com.np>
Cc: linux-kernel@vger.kernel.org
Subject: Re: upgrade linux kernel
Date: Sun, 13 May 2007 14:31:22 +0200	[thread overview]
Message-ID: <5a4c581d0705130531v4679efabgd2ffed96af72862d@mail.gmail.com> (raw)
In-Reply-To: <2417.63.219.2.2.1179056431.squirrel@mail.websurfer.com.np>

On 5/13/07, umesh@websurfer.com.np <umesh@websurfer.com.np> wrote:
> I am upgrading kernel from 2.4.20-8(default in RH9) to 2.6.xx. when I do
> "make" command it gives some output and finally get error saying that,
>
> "BFD: Warning: Writing section '.bss' to huge ( ie negative) file offset
> 0xc0244000. "
>
>  "Objcopy: arch/i386/boot/compressed/vmlinux.bin: file truncated"
>
> "make[2]:***[ arch/i386/boot/compressed/vmlinux.bin] Error 1"
>
>  "make[1]: ***[ arch/i386/boot/compressed/vmlinux] Error 2"
>
>  "make: *** [bzImage] Error 2"

A quick round of googling brings up this

http://www.uwsg.iu.edu/hypermail/linux/kernel/0410.3/0205.html

 where the issue was that binutils were too old to compile the
 newer kernels. More generically, RH9 is now really ancient,
 and you'd probably make your life much easier by upgrading
 to more recent distributions.

If you intend to stay on RH9, please have a look at the
 /usr/src/linux/Documentation/Changes file, it will give you
 a first idea of how much stuff you need to upgrade on RH9.

--alessandro

 "Did you get married but forgot to get divorced ?"

     (Danny and Dusty, 'The Good Old Days')

  reply	other threads:[~2007-05-13 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13 11:40 umesh
2007-05-13 12:31 ` Alessandro Suardi [this message]
2007-05-14  1:03 ` Bill Davidsen

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=5a4c581d0705130531v4679efabgd2ffed96af72862d@mail.gmail.com \
    --to=alessandro.suardi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=umesh@websurfer.com.np \
    /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

all inboxes | Powered by JetHome®