From: John Snow <jsnow@redhat.com>
To: Anand J <anand.indukala@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -Werror=tautological-compare error with -save-temps on fedora 24 gcc 6.2.1
Date: Mon, 17 Oct 2016 10:02:23 -0400 [thread overview]
Message-ID: <fbc9e37a-9d8a-04fb-db78-6b277c6b9cb5@redhat.com> (raw)
In-Reply-To: <CANDALvmcYYJU4bsfNfV2U_za_Ua0OE=73NgghCjJZ3VJuwzf6A@mail.gmail.com>
On 10/16/2016 03:08 AM, Anand J wrote:
> Hi,
>
> I'm using gcc 6.2.1 for compiling qemu with following options in Fedora 24
>
> ../../../configure --enable-debug --extra-cflags="-save-temps"
> make
>
> and getting following error.
>
> * CC ui/gtk.o*
> *qemu/ui/gtk.c: In function ‘gd_map_keycode’:*
> *qemu/ui/gtk.c:1030:21: error: self-comparison always evaluates to true
> [-Werror=tautological-compare]*
> * } else if (GDK_IS_X11_DISPLAY(dpy) && gdk_keycode < 158) {*
> * ^~*
> *qemu/ui/gtk.c: In function ‘gd_set_keycode_type’:*
> *qemu/ui/gtk.c:2123:18: error: self-comparison always evaluates to true
> [-Werror=tautological-compare]*
> * if (GDK_IS_X11_DISPLAY(display)) {*
> * ^~*
> *cc1: all warnings being treated as errors*
> *qemu/rules.mak:60: recipe for target 'ui/gtk.o' failed*
> *make: *** [ui/gtk.o] Error 1*
>
>
>
> Build works fine without -save-temps options. Does anybody know how to fix
> this?
>
> Thanks,
> Anand
>
Reminds me of a CCACHE + clang problem. Try disabling ccache to see if
that improves matters for you. Otherwise, I'd just start disabling
errors as long as you want to be using the save temps option with
-Wno-tautological-compare for now.
prev parent reply other threads:[~2016-10-17 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 7:08 [Qemu-devel] -Werror=tautological-compare error with -save-temps on fedora 24 gcc 6.2.1 Anand J
2016-10-17 14:02 ` John Snow [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=fbc9e37a-9d8a-04fb-db78-6b277c6b9cb5@redhat.com \
--to=jsnow@redhat.com \
--cc=anand.indukala@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 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).