From: Tim Post <tim.post@netkinetics.net>
To: xen-devel@lists.xensource.com
Subject: Which GCC is best for building Xen?
Date: Sun, 29 Jul 2007 12:07:56 +0800 [thread overview]
Message-ID: <1185682076.6365.188.camel@localhost.localdomain> (raw)
Hello to all,
Am I headed for trouble continuing to use gcc 3.4 to build Xen ? I find
gcc 4.1 just too noisy for my own comfort because I disagree with many
of its warnings. I have both installed, I lean on 3.4 most.
I know they are only warnings, but they indicate gcc is doing something
it didn't used to do before. I spent a while trying to study the two to
answer this one for myself but I found it best to ask. I have enough on
my plate just becoming proficient with C, much less its compiler :)
Am I ok to continue with 3.4?
Please reply to me (cc), I am not a subscriber.
Kind regards in advance,
--Tim
next reply other threads:[~2007-07-29 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 4:07 Tim Post [this message]
2007-07-30 18:13 ` Which GCC is best for building Xen? Keir Fraser
2007-08-02 7:00 ` pradeep singh rautela
2007-08-02 7:29 ` Keir Fraser
2007-08-02 7:36 ` pradeep singh rautela
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=1185682076.6365.188.camel@localhost.localdomain \
--to=tim.post@netkinetics.net \
--cc=xen-devel@lists.xensource.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 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.