From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] Problem compiling under mingw32
Date: Sat, 03 Jul 2004 21:54:08 +0200 [thread overview]
Message-ID: <1088884447.7257.2037.camel@rapid> (raw)
In-Reply-To: <E1BgqPf-0005GZ-OU@lists.gnu.org>
On Sat, 2004-07-03 at 21:40, claunia@claunia.com wrote:
> Patch applied, but it does not solve the no text output if no under msys.
>
> Also I think that the patch should be commited to CVS.
Sure not !
It completely breaks the PPC emulation:
with this patch, there is no link register anymore, so the PPC code
can't call or return from functions anymore !
> ginal-----
> > De: qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org
> > [mailto:qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org]
> > En nombre de Filip Navara
> > Enviado el: sábado, 03 de julio de 2004 20:13
> > Para: qemu-devel@nongnu.org
> > Asunto: Re: [Qemu-devel] Problem compiling under mingw32
> >
> >
> > Natalia Portillo wrote:
> >
> > >When I try to compile the lastest CVS QEMU from mingw32
> > >qemu-system-ppc-softmmu shows an error (attached below), and the
> > >qemu-system-i386-softmmu only shows standard output (help
> > and monitor)
> > >when running under MSYS, under the win32 command line it
> > shows nothing.
> > >
> > >Any idea?
> > >
> > Please, please...not again. I have sent patch for this two
> > times to the list, please search the archives.
> >
> > Regards,
> > Filip
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2004-07-03 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 19:40 [Qemu-devel] Problem compiling under mingw32 claunia
2004-07-03 19:54 ` J. Mayer [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-03 20:05 Natalia Portillo
2004-07-03 18:34 [Qemu-devel] more OS X patch help Fred Hope
2004-07-03 19:10 ` [Qemu-devel] Problem compiling under mingw32 Natalia Portillo
2004-07-03 19:12 ` Filip Navara
2004-07-04 5:25 ` kazu
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=1088884447.7257.2037.camel@rapid \
--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).