From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Cq3sk-0002q1-9x
	for qemu-devel@nongnu.org; Sun, 16 Jan 2005 01:27:27 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Cq3se-0002lp-QS
	for qemu-devel@nongnu.org; Sun, 16 Jan 2005 01:27:21 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Cq3sb-0002kf-Bo
	for qemu-devel@nongnu.org; Sun, 16 Jan 2005 01:27:17 -0500
Received: from [64.233.170.205] (helo=rproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1Cq3aJ-0000fb-Q4
	for qemu-devel@nongnu.org; Sun, 16 Jan 2005 01:08:23 -0500
Received: by rproxy.gmail.com with SMTP id i8so265549rne
	for <qemu-devel@nongnu.org>; Sat, 15 Jan 2005 22:08:22 -0800 (PST)
Message-ID: <c10dbf45050115220862087e7b@mail.gmail.com>
Date: Sun, 16 Jan 2005 09:08:22 +0300
From: Phil Krylov <phil.krylov@gmail.com>
Subject: Re: [Qemu-devel] Re: MacOSX CVS build broken
In-Reply-To: <1f1698a605011520285bc01970@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <BE0DEDA1.15F79%johnt@jdtangney.com>
	<1f1698a605011520285bc01970@mail.gmail.com>
Reply-To: Phil Krylov <phil.krylov@gmail.com>, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Tim Douglas <timdoug@gmail.com>, qemu-devel@nongnu.org
Cc: John Tangney <johnt@jdtangney.com>

On Sat, 15 Jan 2005 23:28:31 -0500, Tim Douglas <timdoug@gmail.com> wrote:

> 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.

dyngen should remove output file on error, but it doesn't (possibly
for the purpose of debugging), and the next make invocation doesn't
try to rebuild the corrupt .h file.

-- Ph.