From: Remi Colinet <remi.colinet@free.fr>
To: linux-kernel@vger.kernel.org
Subject: 2.6.9-mm1-U10.3 : failed to objcopy vmlinux into vmlinux.bin
Date: Sat, 23 Oct 2004 01:11:06 +0200 [thread overview]
Message-ID: <4179938A.6050109@free.fr> (raw)
Hi,
I'am getting this error when compiling 2.6.9-mm1-U10.3 (Ingo realtime
patch added to mm tree)
KSYM .tmp_kallsyms3.S
AS .tmp_kallsyms3.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
AS arch/i386/boot/setup.o
LD arch/i386/boot/setup
AS arch/i386/boot/compressed/head.o
CC arch/i386/boot/compressed/misc.o
OBJCOPY arch/i386/boot/compressed/vmlinux.bin
BFD: Warning: Writing section `.bss' to huge (ie negative) file offset
0xc05c6000.
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
[root@tigre01 im]# objdump -h ./vmlinux
./vmlinux: file format elf32-i386
Sections:
Idx Name Size VMA LMA File off Algn
0 .text 0037d80e c0100000 00100000 00001000 2**12
CONTENTS, ALLOC, LOAD, READONLY, CODE
1 __ex_table 000013b8 c047d810 0047d810 0037e810 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
2 .rodata 000a8309 c047ebe0 0047ebe0 0037fbe0 2**5
CONTENTS, ALLOC, LOAD, READONLY, DATA
...
23 .exit.text 00001a5b c06ab430 006ab430 005ac430 2**4
CONTENTS, ALLOC, LOAD, READONLY, CODE
24 .init.ramfs 00000086 c06ad000 006ad000 005ae000 2**0
CONTENTS, ALLOC, LOAD, READONLY, DATA
25 .data.percpu 00018938 c06ad100 006ad100 005ae100 2**7
CONTENTS, ALLOC, LOAD, DATA
26 .bss 0006dfa0 c06c6000 c06c6000 005c7000 2**12
CONTENTS, ALLOC, LOAD, DATA
27 .comment 0000c36f 00000000 00000000 00634fa0 2**0
CONTENTS, READONLY
28 .debug_line 0021497b 00000000 00000000 0064130f 2**0
CONTENTS, READONLY, DEBUGGING
Any idea to fix this objcopy error?
Is my vmlinux.bin too big?
Remi
reply other threads:[~2004-10-23 0:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4179938A.6050109@free.fr \
--to=remi.colinet@free.fr \
--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.