From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:57125) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SzZ99-0007Yq-Rb for qemu-devel@nongnu.org; Thu, 09 Aug 2012 16:15:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SzZ98-0000h0-Q8 for qemu-devel@nongnu.org; Thu, 09 Aug 2012 16:15:55 -0400 Received: from mail-gh0-f173.google.com ([209.85.160.173]:46951) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SzZ98-0000gu-Ll for qemu-devel@nongnu.org; Thu, 09 Aug 2012 16:15:54 -0400 Received: by ghrr17 with SMTP id r17so866937ghr.4 for ; Thu, 09 Aug 2012 13:15:54 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1342620628-12751-1-git-send-email-peter.maydell@linaro.org> <1342620628-12751-12-git-send-email-peter.maydell@linaro.org> From: Blue Swirl Date: Thu, 9 Aug 2012 20:15:33 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH 11/11] configure: Check for -Werror causing failures when compiling tests List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Stefan Weil , qemu-devel@nongnu.org, patches@linaro.org On Thu, Aug 9, 2012 at 6:24 PM, Peter Maydell wrote: > On 4 August 2012 18:57, Blue Swirl wrote: >> On Sat, Jul 28, 2012 at 1:48 PM, Peter Maydell wrote: >>> On 28 July 2012 13:31, Blue Swirl wrote: >>>> I'm getting this error, probably because now Valgrind support is enabled: >>>> CC coroutine-ucontext.o >>>> cc1: warnings being treated as errors >>>> /src/qemu/coroutine-ucontext.c:204: error: unknown option after >>>> '#pragma GCC diagnostic' kind >>>> /src/qemu/coroutine-ucontext.c:209: error: unknown option after >>>> '#pragma GCC diagnostic' kind >>>> >>>> Maybe the compiler does not understand this pragma and Valgrind check >>>> should also fail in that case. >>> >>> Yeah, I think this is one of the few tests which want to explicitly >>> check "is this construct going to provoke a compiler warning" -- >>> fix is for that test to explictly put -Werror in the cflags in >>> the compile_prog line. >> >> Now with your Xen configure patches in place, I'm not getting errors >> with this applied except for Clang (which I didn't test earlier). >> Maybe this should be applied. > > Yes, I think that (assuming we are going to go down this route at all) > it would be good to apply this 11/11 patch now in good time before > the freeze. Does anybody want to object? I'll send a patch that fixes configure with Clang. > > thanks > -- PMM