From: "Anderson Lizardo" <anderson.lizardo@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU static build failing with recent toolchain
Date: Sun, 29 Oct 2006 20:27:03 -0400 [thread overview]
Message-ID: <5b5833aa0610291627u6b05baa5pdd62b2582a4d7964@mail.gmail.com> (raw)
Hi,
QEMU static build (both 0.8.2 and CVS) is failing using a recent
toolchain with this message:
gcc-3.4 -g -static -Wl,-T,/tmp/qemu-cvs-20061029/i386.ld -o qemu-arm
main.o syscall.o mmap.o signal.o path.o osdep.o thunk.o elfload.o
linuxload.o flatload.o nwfpe/fpa11.o nwfpe/fpa11_cpdo.o
nwfpe/fpa11_cpdt.o nwfpe/fpa11_cprt.o nwfpe/fpopcode.o
nwfpe/single_cpdo.o nwfpe/double_cpdo.o nwfpe/extended_cpdo.o
arm-semi.o libqemu.a gdbstub.o -lm
/usr/bin/ld: BFD 2.17 Debian GNU/Linux assertion fail
../../binutils-2.17/bfd/elf.c:3878
/usr/bin/ld: qemu-arm: Not enough room for program headers (allocated 5, need 6)
Section to Segment mapping:
Segment Sections...
00: LOAD: .note.ABI-tag .init .text __libc_freeres_fn
.fini .rodata .rodata.cst4 .eh_frame .rodata.str1.1 .rodata.str1.4
.rodata.str4.4 .gcc_except_table __libc_subfreeres __libc_atexit
.rodata.str1.32
01: LOAD: .data .jcr .data.rel.ro .tdata .ctors .dtors .got .bss
02: LOAD: .tbss __libc_freeres_ptrs
03: NOTE: .note.ABI-tag
04: TLS: .tdata .ctors
05: STACK:
/usr/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status
make: *** [qemu-arm] Error 1
make: Leaving directory `/tmp/qemu-cvs-20061029/arm-user'
I've tested removing the linker script option
"-Wl,-T,<src_dir>/i386.ld" and it compiled fine. Maybe this script is
broken or is not necessary for recent binutils versions?
Information about my system:
- x86 host
- gcc-3.4 (GCC) 3.4.6 (Ubuntu 3.4.6-3ubuntu1)
- glibc 2.4
- binutils 2.17
Regards,
--
Anderson Lizardo
reply other threads:[~2006-10-30 0:27 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=5b5833aa0610291627u6b05baa5pdd62b2582a4d7964@mail.gmail.com \
--to=anderson.lizardo@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).