From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: Ronan Keryell <Ronan.Keryell@enstb.org>
Subject: Re: [Qemu-devel] qemu-i386 does not start on x86_64 or i686
Date: Sat, 20 Oct 2007 01:18:31 -0500 [thread overview]
Message-ID: <200710200118.31273.rob@landley.net> (raw)
In-Reply-To: <87ve945c51.fsf@an-dro.enstb.org>
On Thursday 18 October 2007 4:46:50 pm Ronan Keryell wrote:
> Anybody kind enough to have a look at :
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446868
>
> I've asked some other people and they hit the same issue.
> It's not clear to me where the bug is since it happens very early in the
> starting process...
>
> Thank you,
There have been several earlier threads on this. Here's one I started back in
June: http://lists.gnu.org/archive/html/qemu-devel/2007-06/msg00303.html
It was still broken, last I checked. I'd try to do a git bisect, but 0.9.0
was still broken and if you go back too far it can't find "gcc-3.4" and barfs
because the gcc everything else in the world builds with is 4.x. (What broke
it was moving the system to glibc 2.5, I.E. upgrading Ubuntu to 7.04. Old
versions of qemu don't run against that either.)
It only affects user mode, not system mode, and only the i386 target, so I
just delete that executable after the install so nothing tries to use it.
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2007-10-20 6:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 21:46 [Qemu-devel] qemu-i386 does not start on x86_64 or i686 Ronan Keryell
2007-10-20 6:18 ` Rob Landley [this message]
2007-10-22 13:44 ` Thayne Harbaugh
2007-10-26 0:52 ` Rob Landley
2007-10-26 1:19 ` Thayne Harbaugh
2007-10-26 19:15 ` Rob Landley
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=200710200118.31273.rob@landley.net \
--to=rob@landley.net \
--cc=Ronan.Keryell@enstb.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).