From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Mark Guertin <mguertin@macdiscussion.com>
Subject: Re: [Qemu-devel] Problem installing WIndows
Date: Wed, 27 Jul 2005 16:11:34 +0100 [thread overview]
Message-ID: <200507271611.35670.paul@codesourcery.com> (raw)
In-Reply-To: <964F12DB-FB96-4E81-AEE7-77CE8DDA067D@macdiscussion.com>
On Wednesday 27 July 2005 15:43, Mark Guertin wrote:
> Gcc 4.x does not. Getting dyngen problems here when trying but I
> haven't had time to chase anything down on it yet.
>
> dyngen: blr expected at the end of op_bfsw_TO_cc
>
> sure enough, after a quick objdump there is no blr (or variation).
> Figured this is likely a known thing as gcc 4.x is kind of bleeding
> edge.
See the 3rd Q in http://www.geocities.com/nixling_gone/faq.html
Paul
next prev parent reply other threads:[~2005-07-27 15:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 12:20 [Qemu-devel] Problem installing WIndows Antony Gelberg
2005-07-26 13:26 ` Hetz Ben Hamo
2005-07-26 13:40 ` Antony Gelberg
2005-07-27 9:57 ` Antony Gelberg
2005-07-27 11:03 ` Christian MICHON
2005-07-27 11:56 ` Antony Gelberg
2005-07-27 12:32 ` Christian MICHON
2005-07-27 12:45 ` Paul Brook
2005-07-27 14:15 ` [Qemu-devel] Kqemu for windows more free than kqemu for linux? Elefterios Stamatogiannakis
2005-07-27 14:42 ` Paul Brook
2005-07-27 14:24 ` [Qemu-devel] Kqemu and qvm86 for windows Elefterios Stamatogiannakis
2005-07-27 14:43 ` [Qemu-devel] Problem installing WIndows Mark Guertin
2005-07-27 15:11 ` Paul Brook [this message]
2005-07-27 17:57 ` Mark Guertin
2005-07-27 18:06 ` Paul Brook
2005-07-27 19:31 ` Mark Guertin
2005-07-27 14:48 ` compilation problems (was: [Qemu-devel] Problem installing WIndows) Thomas Schwinge
2005-07-27 12:33 ` [Qemu-devel] Problem installing WIndows Doctor Bill
2005-07-27 13:21 ` Antony Gelberg
2005-07-27 13:49 ` Hetz Ben Hamo
2005-07-27 13:54 ` Paul Brook
2005-07-28 16:55 ` Antony Gelberg
2005-07-28 17:04 ` Filip Navara
2005-07-28 18:12 ` Jim C. Brown
2005-07-27 13:58 ` Christian MICHON
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=200507271611.35670.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=mguertin@macdiscussion.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 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.