From: Mike Frysinger <vapier@gentoo.org>
To: qemu-devel@nongnu.org
Cc: Sunil Amitkumar Janki <devel.sjanki@gmail.com>
Subject: Re: [Qemu-devel] WE NEED GCC 4 please
Date: Sun, 20 Jan 2008 17:56:12 -0500 [thread overview]
Message-ID: <200801201756.13548.vapier@gentoo.org> (raw)
In-Reply-To: <767364c50801201438j37245af9t6d7644f7d4a73d54@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On Sunday 20 January 2008, Sunil Amitkumar Janki wrote:
> Ignoring the fact that the original poster wrote in all caps and can't
> contribute much to qemu development, what is being done or who can
> give directions on what would have to be done to make qemu build using
> gcc4. I'd prefer it too that I wouldn't have to keep an old gcc 3.x
> compiler around specifically to build qemu, so what can we do about
> that?
as i said, review the archives and you'll find many discussions with real
information on the topic
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-01-20 22:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 19:31 Re : [Qemu-devel] WE NEED GCC 4 please Sylvain Petreolle
2008-01-20 20:11 ` Mike Frysinger
2008-01-20 21:14 ` Johannes Schindelin
2008-01-20 22:26 ` Mike Frysinger
2008-01-20 22:38 ` Sunil Amitkumar Janki
2008-01-20 22:56 ` Mike Frysinger [this message]
2008-01-20 23:04 ` Philip Boulain
2008-01-20 22:59 ` Andreas Färber
2008-01-20 23:40 ` Johannes Schindelin
2008-01-21 3:39 ` Mulyadi Santosa
2008-01-21 7:19 ` Alexander Graf
2008-01-21 11:18 ` Johannes Schindelin
2008-01-21 11:30 ` Mulyadi Santosa
2008-01-21 12:45 ` Andreas Färber
2008-01-21 13:02 ` Johannes Schindelin
2008-01-21 13:51 ` Julian Seward
2008-01-21 14:58 ` Ronan Keryell
2008-01-21 15:36 ` Paul Brook
-- strict thread matches above, loose matches on Subject: below --
2008-01-20 2:34 renatogallo
2008-01-20 18:40 ` Jérôme PRIOR
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=200801201756.13548.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=devel.sjanki@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.