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 Developers <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 4/4] configure: Add workaround for ccache and clang
Date: Mon, 23 Mar 2015 12:32:43 -0400	[thread overview]
Message-ID: <5510402B.9050506@redhat.com> (raw)
In-Reply-To: <CAFEAcA-fPFKjpiBDez4p_FmFfb7otFBB_Zv-6fKJj-EyvX5aaw@mail.gmail.com>



On 03/23/2015 11:14 AM, Peter Maydell wrote:
> On 23 March 2015 at 14:52, John Snow <jsnow@redhat.com> wrote:
>> On 03/23/2015 09:11 AM, Peter Maydell wrote:
>>> This is really working around a bug in either ccache or
>>> in the way Fedora has configured ccache, so I kind of
>>> feel it ought to be dealt with there. However I don't
>>> object too much to our including the workaround in our
>>> configure...
>
>> I feel like it might be an inescapable consequence of using both ccache and
>> clang together on any system, not just Fedora.
>
> Right, but it's not *QEMU* specific, so it would be better

OK, true.

> if either (a) ccache automatically enabled this if it
> noticed it was being run for clang or (b) Fedora automatically
> enabled this in their aliases which make 'clang' automatically
> be "clang run via ccache".
>
> Is there a bug filed against Fedora for this?
>
> -- PMM
>

Not that I can see on the RH or ccache/LLVM bugzillas at a quick glance. 
I can try to file something for ccache after I look a little more carefully.

In the meantime, until things improve, I think this workaround is sane 
if we want to deal with clang failures less.

I'll clean up the other minor comments and resubmit.

--js

      reply	other threads:[~2015-03-23 16:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 19:01 [Qemu-devel] [PATCH v3 0/4] configure: clang 3.5.0 build fixes John Snow
2015-03-19 19:01 ` [Qemu-devel] [PATCH v3 1/4] configure: handle clang -nopie argument warning John Snow
2015-03-19 19:01 ` [Qemu-devel] [PATCH v3 2/4] configure: factor out supported flag check John Snow
2015-03-23 13:03   ` Stefan Hajnoczi
2015-03-23 14:44     ` John Snow
2015-03-23 14:48       ` Paolo Bonzini
2015-03-23 14:50       ` Stefan Hajnoczi
2015-03-19 19:01 ` [Qemu-devel] [PATCH v3 3/4] configure: silence glib unknown attribute __alloc_size__ John Snow
2015-03-19 19:01 ` [Qemu-devel] [PATCH v3 4/4] configure: Add workaround for ccache and clang John Snow
2015-03-23 12:58   ` Stefan Hajnoczi
2015-03-23 13:11   ` Peter Maydell
2015-03-23 14:52     ` John Snow
2015-03-23 15:14       ` Peter Maydell
2015-03-23 16:32         ` 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=5510402B.9050506@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).