From: Emmanuel Charpentier <charpent@bacbuc.dyndns.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Problem compiling with gcc 3.3 on 2.6.14 (Debian)
Date: Mon, 28 Nov 2005 23:27:30 +0100 [thread overview]
Message-ID: <438B8452.6070309@bacbuc.dyndns.org> (raw)
In-Reply-To: <20051128165951.GA28507@jbrown.mylinuxbox.org>
Jim C. Brown wrote:
> On Mon, Nov 28, 2005 at 09:46:02AM +0100, Emmanuel Charpentier wrote:
>
>>Dear List,
>>
>>I recently upgraded to Linux 2.6.14 (as compiled as a 686 Debian
>>package), and found that this distribution, too, has switched to GCC 4
>>for kernel.
>>
>>I tried to recompile a plain vanilla qemu 0.7.2 tarball : I switched to
>>gcc 3.3 for this (in /usr/bin : ln -sf gcc-3.3 gcc ; ln -sf gccbug-3.3
>>gccbug ; ln -sf cpp-3.3 cpp ), planning to switch back to GCC 4 for
>>recompilation of the kqemu subdirectory. This failed.
>>
>
>
> Strange. Haven't heard of this one before.
>
> Compiling the kqemu module should use the same compiler that the kernel uses
> anyways. It doesn't use the same one that qemu uses, but the one in the kernel's
> Makefile.
I knew that ; that's whi I switched back to gcc 3.3 for compilation of
the main package, planning to go back to GCC 4 for kqemu. but comiling
this one needs a correctly configured qemu tree.
> I also notice that your error seems to be with qemu-i386. This binary doesn't use
> kqemu at all, so either don't use kqemu (if all you care about is i386-user) or
> compile i386-softmmu only (if you want to use kqemu and don't care aboui i386-user).
I''l try that. But the point isn't here. That's the first time I saw
such a problem with qemu. Since what has changed is the kernel (and
probably parts of the compilation system, BTW : Debian instable is ...
well ... somewhat unstable...)
> It is hard to make out the problem when the error messages aren't in english, btw.
OK : I'll translate the error messages :
All is fine and dandy up to the "compilation" (linking, in fact) of
qemu-i386 :
> gcc -g -Wl,-shared -o qemu-i386 elfload.o main.o syscall.o mmap.o
> signal.o path.o osdep.o thunk.o vm86.o libqemu.a gdbstub.o -lm >
/usr/bin/ld: section .note.ABI-tag [0000000000000468 ->
> 0000000000000487] chevauche la section .hash [0000000000000114 ->
> 00000000000027d3]
> /usr/bin/ld: qemu-i386: Not enough room for program headers
(allocated > 8, need 9)
> /usr/bin/ld: édition de lien finale en échec: Mauvaise valeur
/usr/bin/ld: final linking failed: bad value
> collect2: ld a retourné 1 code d'état d'exécution
collect2 returned 1 return value
> make[1]: *** [qemu-i386] Erreur 1
> make[1]: *** [qemu-i386] Error 1
> make[1]: Leaving directory
> `/home/charpent/qemu-source/qemu-0.7.2/i386-user'
> make: *** [all] Erreur 1
make: *** [all] Error 1
Hoping this helps...
Emmanuel Charpentier
next prev parent reply other threads:[~2005-11-28 23:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 8:46 [Qemu-devel] Problem compiling with gcc 3.3 on 2.6.14 (Debian) Emmanuel Charpentier
2005-11-28 16:59 ` Jim C. Brown
2005-11-28 19:41 ` Natalia Portillo
2005-11-28 21:24 ` [Qemu-devel] Debian blues (Re: Problem compiling with gcc 3.3 on 2.6.14 (Debian)) Emmanuel Charpentier
2005-11-28 22:35 ` Daniel Jacobowitz
2005-11-29 8:58 ` [Qemu-devel] " Emmanuel Charpentier
2005-11-29 11:00 ` Gwenole Beauchesne
2005-11-29 14:02 ` carlo.andreoli
2005-11-29 22:41 ` Pascal Terjan
2005-11-30 8:13 ` carlo.andreoli
2005-11-29 21:07 ` Emmanuel Charpentier
2005-11-28 21:09 ` [Qemu-devel] Re: Problem compiling with gcc 3.3 on 2.6.14 (Debian) Emmanuel Charpentier
2005-11-28 22:27 ` Emmanuel Charpentier [this message]
2005-11-29 1:06 ` Brad Watson
2005-11-29 1:07 ` Brad Watson
2005-11-29 10:32 ` Sylvain Petreolle
2005-11-29 21:09 ` Emmanuel Charpentier
2005-11-30 8:25 ` [Qemu-devel] Problem compiling with gcc 3.3 on 2.6.14 Jernej Simončič
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=438B8452.6070309@bacbuc.dyndns.org \
--to=charpent@bacbuc.dyndns.org \
--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).