qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Emmanuel Charpentier <charpent@bacbuc.dyndns.org>
Subject: Re: [Qemu-devel] Current state of GCC 4 (non-)"support" on x86-64 ?
Date: Fri, 30 Sep 2005 17:18:02 +0100	[thread overview]
Message-ID: <200509301718.06167.paul@codesourcery.com> (raw)
In-Reply-To: <433D60D0.8040601@bacbuc.dyndns.org>

On Friday 30 September 2005 16:59, Emmanuel Charpentier wrote:
> Dear list,
>
> I understand that the current "official" qemu needs gcc 3.x and won't
> compile with gcc 4.x

You can compile qemu and the kernel module with different compilers.

Paul

  reply	other threads:[~2005-09-30 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 15:59 [Qemu-devel] Current state of GCC 4 (non-)"support" on x86-64 ? Emmanuel Charpentier
2005-09-30 16:18 ` Paul Brook [this message]
2005-09-30 18:40   ` Jim C. Brown
2005-09-30 21:30 ` Henrik Nordstrom
2005-10-09 17:54 ` [Qemu-devel] " Michel Pelletier
2005-10-10  8:55   ` Gwenole Beauchesne

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=200509301718.06167.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=charpent@bacbuc.dyndns.org \
    --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).