From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Cq2je-0000wD-6b for qemu-devel@nongnu.org; Sun, 16 Jan 2005 00:13:58 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Cq2b9-0008Co-AR for qemu-devel@nongnu.org; Sun, 16 Jan 2005 00:05:15 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cq2b7-00082t-Op for qemu-devel@nongnu.org; Sun, 16 Jan 2005 00:05:09 -0500 Received: from [64.233.170.195] (helo=rproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Cq21h-0004Ak-0z for qemu-devel@nongnu.org; Sat, 15 Jan 2005 23:28:33 -0500 Received: by rproxy.gmail.com with SMTP id c16so166418rne for ; Sat, 15 Jan 2005 20:28:31 -0800 (PST) Message-ID: <1f1698a605011520285bc01970@mail.gmail.com> Date: Sat, 15 Jan 2005 23:28:31 -0500 From: Tim Douglas In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: Subject: [Qemu-devel] Re: MacOSX CVS build broken Reply-To: Tim Douglas , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: John Tangney , qemu-devel@nongnu.org On Fri, 14 Jan 2005 21:44:01 -0800, John Tangney 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