From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: devnull@geisel.info
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17-pre5 "make bzImage" fails
Date: Thu, 06 Dec 2001 14:53:16 -0500 [thread overview]
Message-ID: <3C0FCCAC.CE6905D5@mandrakesoft.com> (raw)
In-Reply-To: <20011206195025.GA9599@geisel.info>
devnull@geisel.info wrote:
>
> Hi,
>
> I switched from 2.4.16 to 2.4.17-pre5 without changing config and now
> "make bzImage" fails with the following error:
>
> ----------------------------------------------------------------------------
> tmppiggy=_tmp_$$piggy; \
> rm -f $tmppiggy $tmppiggy.gz $tmppiggy.lnk; \
> objcopy -O binary -R .note -R .comment -S /usr/src/linux/vmlinux
> $tmppiggy; \
> gzip -f -9 < $tmppiggy > $tmppiggy.gz; \
> echo "SECTIONS { .data : { input_len = .; LONG(input_data_end -
> input_data) input_data = .; *(.data) input_data_end = .; }}" >
> $tmppiggy.lnk; \
> ld -m elf_i386 -r -o piggy.o -b binary $tmppiggy.gz -b elf32-i386 -T
> $tmppiggy.lnk; \
> rm -f $tmppiggy $tmppiggy.gz $tmppiggy.lnk
> gcc -D__ASSEMBLY__ -D__KERNEL__ -I/usr/src/linux/include -traditional -c
> head.S
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
> -pipe -mpreferred-stack-boundary=2 -march=athlon -c misc.c
> ld -m elf_i386 -Ttext 0x100000 -e startup_32 -o bvmlinux head.o misc.o
> piggy.o
> ld: bvmlinux: Not enough room for program headers (allocated 2, need 3)
> ld: final link failed: Bad value
did you upgrade your binutils recently?
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-12-06 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 19:50 2.4.17-pre5 "make bzImage" fails devnull
2001-12-06 19:53 ` Jeff Garzik [this message]
2001-12-06 19:57 ` devnull
2001-12-07 6:07 ` skidley
2001-12-07 7:24 ` safemode
2001-12-07 15:29 ` Chmouel Boudjnah
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=3C0FCCAC.CE6905D5@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=devnull@geisel.info \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.