qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jocelyn Mayer <l_indien@magic.fr>
To: qemu mailing list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] powerpc (debian/sid) woes
Date: 30 Jul 2003 16:27:33 +0200	[thread overview]
Message-ID: <1059575253.1749.817.camel@jma1.dev.netgem.com> (raw)
In-Reply-To: <1059514392.1750.805.camel@jma1.dev.netgem.com>

On Tue, 2003-07-29 at 23:33, Jocelyn Mayer wrote:
> On Tue, 2003-07-29 at 22:57, Fabrice Bellard wrote:
> > The problem is that I don't have access to a gcc-3.3 powerpc based system...
> > 
> > Fabrice.
> > 
> <...snip...>
> 
> I got one with gcc 3.2.
> I'll make some tries when I have an up-to-date qemu-x86 repository.
> With the version I have today (about one week aged CVS co),
> I have no probleme.
> The kernel is 2.4.21-rc7, I must also check the glibc version.
> I compiled today an up-to-date CVS qemu for PPC target,
> so syscall.c did compile, with a 2.6.0-test1 kernel.
> 
> I may also try to update my compiler to gcc-3.3, if I'm not too lazy :=)

I compiled a fresh gcc 3.3 tonight.
I've been able to build all qemu emulator targets,
after a cvs update with no problems.
My config is now:
kernel 2.6.0-test1
glibc 2.2.5
gcc 3.3
binutils 1.13

I also compiled on a PC at the same time.
The only problem I had was the compilation of signal.c in debug mode
on the PC (kernel 2.4.21-pre7, glibc 2.2.5,gcc 2.95.3, binutils 2.13)
I had to use this patch:

Index: signal.c
===================================================================
RCS file: /cvsroot/qemu/qemu/signal.c,v
retrieving revision 1.17
diff -u -d -w -B -b -d -p -r1.17 signal.c
--- signal.c    13 Jul 2003 17:33:54 -0000      1.17
+++ signal.c    30 Jul 2003 14:22:13 -0000
@@ -378,16 +378,16 @@ static void dump_regs(struct ucontext *u
             "EAX=%08x EBX=%08x ECX=%08x EDX=%08x\n"
             "ESI=%08x EDI=%08x EBP=%08x ESP=%08x\n"
             "EFL=%08x EIP=%08x\n",
-            uc->uc_mcontext.gregs[EAX],
-            uc->uc_mcontext.gregs[EBX],
-            uc->uc_mcontext.gregs[ECX],
-            uc->uc_mcontext.gregs[EDX],
-            uc->uc_mcontext.gregs[ESI],
-            uc->uc_mcontext.gregs[EDI],
-            uc->uc_mcontext.gregs[EBP],
-            uc->uc_mcontext.gregs[ESP],
-            uc->uc_mcontext.gregs[EFL],
-            uc->uc_mcontext.gregs[EIP]);
+            uc->uc_mcontext.gregs[REG_EAX],
+            uc->uc_mcontext.gregs[REG_EBX],
+            uc->uc_mcontext.gregs[REG_ECX],
+            uc->uc_mcontext.gregs[REG_EDX],
+            uc->uc_mcontext.gregs[REG_ESI],
+            uc->uc_mcontext.gregs[REG_EDI],
+            uc->uc_mcontext.gregs[REG_EBP],
+            uc->uc_mcontext.gregs[REG_ESP],
+            uc->uc_mcontext.gregs[REG_EFL],
+            uc->uc_mcontext.gregs[REG_EIP]);
 }
 #else
 static void dump_regs(struct ucontext *uc)

Regards.

-- 
Jocelyn Mayer <l_indien@magic.fr>

  reply	other threads:[~2003-07-30 14:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 20:09 [Qemu-devel] powerpc (debian/sid) woes Christof Petig
2003-07-29 20:57 ` Fabrice Bellard
2003-07-29 21:33   ` Jocelyn Mayer
2003-07-30 14:27     ` Jocelyn Mayer [this message]
2003-08-05 11:18       ` Christof Petig
2003-08-05 12:26         ` Herbert Pötzl
2003-08-05 13:40         ` Jocelyn Mayer

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=1059575253.1749.817.camel@jma1.dev.netgem.com \
    --to=l_indien@magic.fr \
    --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).