All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christof Petig <christof@petig-baender.de>
To: Klokan Petr Pridal <xpridal@informatics.muni.cz>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEmu on debian PPC unstable
Date: Fri, 07 Nov 2003 09:16:11 +0100	[thread overview]
Message-ID: <3FAB54CB.9020109@petig-baender.de> (raw)
In-Reply-To: <20031107004225.B5025837@aisa.fi.muni.cz>

Klokan Petr Pridal schrieb:
> Hi,
> 
> I have read your message in QEmu mailing-list about compilation of
> QEmu on Debian UNSTABLE PowerPC..
> 
> Please, are you running Qemu on that that distribution? Have you some
> newer Wine as you noticed in mail? Could you send me binaries or give
> me an advice how to compile qemu-0.5?

I am running today CVS's qemu on today's debian/sid. No problem with 
qemu-i386 and Wine 20030813 (on debian/woody+bunk+gnome2.2). [Today 
CVS's Wine is just compiling]

[gcc 3.3.2, XFree 4.3.0]

Only two minor problems left: images tend to get color shifted (xlib 
bug) and some apps have font problems (wine configuration mess up, AFAICT).

> I have failed with compilation with "more than 10 operands in asm"
> call - same as you write in conference. (When use gcc-3.3) Is this
> bug patched somewhere?

I suspect that a newer version of kernel-header-something fixed that for me.

Only sparc has issues:
[...]
/home/christof/sourceforge/qemu/target-sparc/op.c:421: Warnung: unused 
variable `V'
/tmp/ccuAOhsB.s: Assembler messages:
/tmp/ccuAOhsB.s:2985: Error: symbol `__op_label0.__func__' is already 
defined
make[1]: *** [op.o] Fehler 1
make[1]: Leaving directory `/home/christof/sourceforge/qemu/sparc-user'

    Christof

PS: Sending binary in private mail.

       reply	other threads:[~2003-11-07  8:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031107004225.B5025837@aisa.fi.muni.cz>
2003-11-07  8:16 ` Christof Petig [this message]
2003-11-09 14:46   ` [Qemu-devel] Re: QEmu on debian PPC unstable Fabrice Bellard

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=3FAB54CB.9020109@petig-baender.de \
    --to=christof@petig-baender.de \
    --cc=qemu-devel@nongnu.org \
    --cc=xpridal@informatics.muni.cz \
    /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.