qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] clang 3.5.0 errors
Date: Tue, 17 Mar 2015 15:59:26 -0400	[thread overview]
Message-ID: <5508879E.2050809@redhat.com> (raw)
In-Reply-To: <CAFEAcA-4JK7-ZL5RyEjv4u7jOfk5upqPyJ6E3pitMpAgdK9Zyg@mail.gmail.com>



On 03/17/2015 03:34 PM, Peter Maydell wrote:
> On 17 March 2015 at 19:30, John Snow <jsnow@redhat.com> wrote:
>> -Wunused-command-line-argument currently complains about the many include
>> flags passed to each CC incantation -- presumably this is not really
>> fixable, because we'd have to fix our Makefile to be a lot smarter than it
>> is. We probably need to stifle these warnings conditionally like
>> unknown-attributes, above.
>
> Do you see this with really just --cc=clang ? I see these warnings
> if I try to use clang with ccache, but I believe that's a ccache bug.
>
> -- PMM
>

Not /intentionally/ invoking ccache:

../../configure --cc=clang --host-cc=clang --enable-debug 
--extra-cflags="-Werror -Wno-unknown-attributes 
-Wno-parentheses-equality -Wno-self-assign -Wno-tautological-compare"

But that's because:

which clang
/usr/lib64/ccache/clang

Which is definitely not of my own doing -- seems to be a default in 
Fedora 21.

  reply	other threads:[~2015-03-17 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 19:30 [Qemu-devel] clang 3.5.0 errors John Snow
2015-03-17 19:34 ` Peter Maydell
2015-03-17 19:59   ` John Snow [this message]
2015-03-17 23:07     ` Peter Maydell
2015-03-18 19:22       ` John Snow
2015-03-18 20:28         ` Peter Maydell
2015-03-18 22:22           ` John Snow
2015-03-18 22:48             ` Peter Maydell

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=5508879E.2050809@redhat.com \
    --to=jsnow@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 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).