qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sim <simvirus@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] compile error ( translate-op.c:36 -op.h:In function `dyng..)
Date: Thu, 20 Jul 2006 11:26:04 +0200	[thread overview]
Message-ID: <d3e73af70607200226k151456c2ra8b05e20253c2493@mail.gmail.com> (raw)
In-Reply-To: <44BF466C.9070908@xtal.rwth-aachen.de>

Hi!

 Sorry, but I have the some problem with qemu-0.8.1

Thanks

> Instead of trying to compile 0.80 you might want to try current
> cvs-version (link can be found on qemu homepage or the dev-list
> archive). It's possible that this problem has been fixed for quite some
> time in cvs.
>

  reply	other threads:[~2006-07-20  9:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-20  8:27 [Qemu-devel] compile error ( translate-op.c:36 -op.h:In function `dyng..) Sim
2006-07-20  9:01 ` Jan Marten Simons
2006-07-20  9:26   ` Sim [this message]
2006-07-20 10:43     ` Sim
2006-07-20 21:04       ` Sim
2006-07-21  9:24         ` Jan Marten Simons
2006-07-21 14:00           ` Sim
2006-07-21 17:41             ` Sim

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=d3e73af70607200226k151456c2ra8b05e20253c2493@mail.gmail.com \
    --to=simvirus@gmail.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 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).