From: Jerone Young <jyoung5@us.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: kvm-ppc-devel@lists.sourceforge.net, kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-ppc-devel] [PATCH] Add -Werror to libkvm compile
Date: Tue, 25 Mar 2008 11:33:09 -0500 [thread overview]
Message-ID: <1206462789.7284.1.camel@thinkpadL> (raw)
In-Reply-To: <92ec769968b9bf27d3489e819bf1bbf8@kernel.crashing.org>
It does work with gcc 4.2.3 . Though no idea if gcc-4.3 & 4.4 would
workout. Though they should. I'll need to to compile them and give them
a try.
On Mon, 2008-03-24 at 20:42 +0100, Segher Boessenkool wrote:
> > This patch adds -Werror to CFLAGS for compilation of libkvm. This
> > should stop complaints about Warnings.
>
> Does libkvm build without warnings using GCC-4.3 (or even GCC-4.4)
> on all supported platforms? If not, please fix that first :-)
>
>
> Segher
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-03-25 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 18:44 [PATCH] Add -Werror to libkvm compile Jerone Young
2008-03-24 19:42 ` [kvm-ppc-devel] " Segher Boessenkool
2008-03-25 16:33 ` Jerone Young [this message]
2008-03-25 17:08 ` Avi Kivity
2008-03-25 19:09 ` Jerone Young
2008-03-26 16:41 ` Avi Kivity
2008-03-24 20:28 ` Anthony Liguori
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=1206462789.7284.1.camel@thinkpadL \
--to=jyoung5@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=kvm-ppc-devel@lists.sourceforge.net \
--cc=segher@kernel.crashing.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