From: Phil Krylov <phil.krylov@gmail.com>
To: Tim Douglas <timdoug@gmail.com>, qemu-devel@nongnu.org
Cc: John Tangney <johnt@jdtangney.com>
Subject: Re: [Qemu-devel] Re: MacOSX CVS build broken
Date: Sun, 16 Jan 2005 09:08:22 +0300 [thread overview]
Message-ID: <c10dbf45050115220862087e7b@mail.gmail.com> (raw)
In-Reply-To: <1f1698a605011520285bc01970@mail.gmail.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.
next prev parent reply other threads:[~2005-01-16 6:27 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 ` [Qemu-devel] Re: MacOSX CVS build broken Tim Douglas
2005-01-16 6:08 ` Phil Krylov [this message]
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=c10dbf45050115220862087e7b@mail.gmail.com \
--to=phil.krylov@gmail.com \
--cc=johnt@jdtangney.com \
--cc=qemu-devel@nongnu.org \
--cc=timdoug@gmail.com \
/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).