qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bob Deblier <bob.deblier@telenet.be>
To: Hetz Ben Hamo <hetz@softier.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU causes internal compiler error in gcc-3.4.2 from	FC3 x86_64
Date: Wed, 10 Nov 2004 16:04:41 +0100	[thread overview]
Message-ID: <1100099082.16579.28.camel@orion> (raw)
In-Reply-To: <200411101517.02618.hetz@softier.com>

On Wed, 2004-11-10 at 15:17 +0200, Hetz Ben Hamo wrote:
> On Wednesday 10 November 2004 14:18, Bob Deblier wrote:
> > F.Y.I.
> >
> > Just posted this bug upstream to RedHat:
> >
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=138627
> 
> Could you try: make clean ; make
> 
> As odd as it seems, I have seen this problem before and thats what "cured" 
> it...
> 
> Thanks,
> Hetz

Tried that first thing - didn't work. The problem is persistent and
reproducible, hence my posting.

Bob

      parent reply	other threads:[~2004-11-10 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 12:18 [Qemu-devel] QEMU causes internal compiler error in gcc-3.4.2 from FC3 x86_64 Bob Deblier
2004-11-10 13:17 ` Hetz Ben Hamo
2004-11-10 13:32   ` Magnus Damm
2004-11-10 15:04   ` Bob Deblier [this message]

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=1100099082.16579.28.camel@orion \
    --to=bob.deblier@telenet.be \
    --cc=hetz@softier.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).