qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: VMiklos <vmiklos@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu 0.8.1 && sparc-user && x86_64
Date: Fri, 19 May 2006 19:34:49 +0200	[thread overview]
Message-ID: <d5a13c80605191034r5e30b330y@mail.gmail.com> (raw)

hi

qemu 0.8.1 (0.8.0, too) fails to compile on x86_64 if sparc-user is
enabled:

gcc-3.3 -Wall -O2 -g -fno-strict-aliasing -I. -I..
-I/var/tmp/fst/src/qemu-0.8.1/target-sparc -I/var/tmp/fst/src/qemu-0.8.1
-I/var/tmp/fst/src/qemu-0.8.1/linux-user
-I/var/tmp/fst/src/qemu-0.8.1/linux-user/sparc -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/var/tmp/fst/src/qemu-0.8.1/fpu -I/var/tmp/fst/src/qemu-0.8.1/slirp -c
-o translate-op.o /var/tmp/fst/src/qemu-0.8.1/translate-op.c
In file included from /var/tmp/fst/src/qemu-0.8.1/translate-op.c:36:
op.h: In function `dyngen_code':
op.h:3759: error: syntax error before '.' token
op.h:3761: error: syntax error before '.' token
make[1]: *** [translate-op.o] Error 1
make[1]: Leaving directory `/var/tmp/fst/src/qemu-0.8.1/sparc-user'
make: *** [all] Error 1

is this a known issue?

thanks,
VMiklos

--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org

                 reply	other threads:[~2006-05-19 17:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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