From: Thomas Sailer <t.sailer@alumni.ethz.ch>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] time for 0.8.3/0.9?
Date: Tue, 26 Dec 2006 01:19:46 +0100 [thread overview]
Message-ID: <1167092386.3284.28.camel@unreal> (raw)
In-Reply-To: <e8ca35370612251324j50dc2aedy4122be27d0984067@mail.gmail.com>
On Mon, 2006-12-25 at 22:24 +0100, Pascal Terjan wrote:
> Could you be more precise ?
> I have been using qemu on x86_64 built with a 64 bits compiler for
> more than 1 year (maybe 2).
I get a qemu segfault during build of http://projects.o-hand.com/poky.
Poky crosscompiles glibc for arm, then tries to run the built localedef
utility using qemu-arm. This step crashes (sig 11) for me under x86_64
using three days old CVS qemu (and also with older qemu). Haven't yet
tried unter x86_32, though, will do next year.
Tom
next prev parent reply other threads:[~2006-12-26 0:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 12:50 [Qemu-devel] time for 0.8.3/0.9? Hetz Ben Hamo
2006-12-24 15:33 ` Werner Dittmann
2006-12-25 21:24 ` Pascal Terjan
2006-12-26 0:19 ` Thomas Sailer [this message]
2006-12-26 9:16 ` Werner Dittmann
2006-12-26 11:09 ` Carlo Marcelo Arenas Belon
2006-12-27 13:19 ` 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=1167092386.3284.28.camel@unreal \
--to=t.sailer@alumni.ethz.ch \
--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).