qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tim Douglas <timdoug@gmail.com>
To: John Tangney <johnt@jdtangney.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: MacOSX CVS build broken
Date: Sat, 15 Jan 2005 23:28:31 -0500	[thread overview]
Message-ID: <1f1698a605011520285bc01970@mail.gmail.com> (raw)
In-Reply-To: <BE0DEDA1.15F79%johnt@jdtangney.com>

On Fri, 14 Jan 2005 21:44:01 -0800, John Tangney <johnt@jdtangney.com> wrote:
> I am still getting the same thing a week later after a fresh cvs update.
> Any hints?

As am I. Check out this interesting log:

gcc -Wall -O2 -g -fno-strict-aliasing -D__powerpc__
-fno-reorder-blocks -fno-optimize-sibling-calls -mdynamic-no-pic -I.
-I/Users/timdoug/Desktop/qemu/target-i386
-I/Users/timdoug/Desktop/qemu -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -I/Users/timdoug/Desktop/qemu/slirp -c -o op.o
/Users/timdoug/Desktop/qemu/target-i386/op.c
In file included from /Users/timdoug/Desktop/qemu/target-i386/exec.h:21,
                 from /Users/timdoug/Desktop/qemu/target-i386/op.c:22:
/Users/timdoug/Desktop/qemu/dyngen-exec.h:38: warning: redefinition of `int8_t'
/usr/include/ppc/types.h:69: warning: `int8_t' previously declared here
/Users/timdoug/Desktop/qemu/dyngen-exec.h:39: warning: redefinition of `int16_t'
/usr/include/ppc/types.h:71: warning: `int16_t' previously declared here
/Users/timdoug/Desktop/qemu/dyngen-exec.h:40: warning: redefinition of `int32_t'
/usr/include/ppc/types.h:73: warning: `int32_t' previously declared here
/Users/timdoug/Desktop/qemu/dyngen-exec.h:44: warning: redefinition of `int64_t'
/usr/include/ppc/types.h:75: warning: `int64_t' previously declared here
../dyngen -o op.h op.o
dyngen: blr expected at the end of op_pmaddwd_mmx
make[1]: *** [op.h] Error 1
make: *** [all] Error 1
DualG5:~/Desktop/qemu timdoug$ make
for d in i386-softmmu; do \
make -C $d all || exit 1 ; \
        done
../dyngen -c -o opc.h op.o
dyngen: blr expected at the end of op_pmaddwd_mmx
make[1]: *** [opc.h] Error 1
make: *** [all] Error 1
DualG5:~/Desktop/qemu timdoug$ make
for d in i386-softmmu; do \
make -C $d all || exit 1 ; \
        done
gcc -Wall -O2 -g -fno-strict-aliasing -D__powerpc__ -I.
-I/Users/timdoug/Desktop/qemu/target-i386
-I/Users/timdoug/Desktop/qemu -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -I/Users/timdoug/Desktop/qemu/slirp -c -o
translate-all.o /Users/timdoug/Desktop/qemu/translate-all.c
/Users/timdoug/Desktop/qemu/translate-all.c: In function `dyngen_code':
/Users/timdoug/Desktop/qemu/translate-all.c:290: error: parse error at
end of input
/Users/timdoug/Desktop/qemu/translate-all.c:56: warning: unused
variable `code_copy_enabled'
make[1]: *** [translate-all.o] Error 1
make: *** [all] Error 1
DualG5:~/Desktop/qemu timdoug$

The first invocation of gcc here makes op.o at 536k. dyngen then
fails, but still makes op.h. The second run of dyngen fails too, but
again it outputs opc.h. And then translate-all.c fails to build
because something is broken in dyngen_code which is in op.h. So
something must indeed be wrong with dyngen or op.c or something else.
Here, though, qemu's internal workings bypass my knowledge, so I've
sent this to qemu-devel too to see what they can figure out.

Cheers,
-Tim

       reply	other threads:[~2005-01-16  5:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BE0DEDA1.15F79%johnt@jdtangney.com>
2005-01-16  4:28 ` Tim Douglas [this message]
2005-01-16  6:08   ` [Qemu-devel] Re: MacOSX CVS build broken Phil Krylov
2005-01-21 22:38   ` Ronald
2005-01-21 23:08     ` Paul Brook
2005-01-21 23:09     ` Johannes Schindelin
2005-01-21 23:14     ` Daniel Egger
2005-01-23 21:11       ` 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=1f1698a605011520285bc01970@mail.gmail.com \
    --to=timdoug@gmail.com \
    --cc=johnt@jdtangney.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).