Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp229341yba; Fri, 5 Apr 2019 05:40:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqy4nEMzdnAcnDSQVKiEIVhlomIeOuS+YxenO1Tm9Nk6/sA5BOM9cq+tyl1PIeZA7U8/4S+g X-Received: by 2002:a62:6504:: with SMTP id z4mr12331865pfb.202.1554468008231; Fri, 05 Apr 2019 05:40:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554468008; cv=none; d=google.com; s=arc-20160816; b=Fc57aoRee7ZC0nKy/a7/Vnj5BLaAry0FDoiqQljpBj9TFxqyEjgCBSIZA2oDfTZvnn QTTt2Ah2uR9zGFsfavRAmyEIEzMi2ldW4bJlAfWcmBtnxbFMXbcBEJEjwbagEULGAhZv LVHgBc9eySzBsBqt6NUB/pSI4L3yUiQzBdEjZrAkgeAD5g+3giOpVBkPYLPLZEqDKuhF WXW3VNdTcy41kF3ydlLIHVgFJMJmEgBdN1xSDTazgYXLAwCu7dZV82C/6yeSjBPWwM3d 44x4cvWdScVzEUcbsduz/A0+OMrxgIpygd795hjOiksl42+2H05JXoX19ThvQbdHxGko QgWw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=I05pzdHWywfglMeKa5ptap/Avz7y5AHiQK16HP3qiJ8=; b=z/U3Nz2hLvv365yoR3n4E0k+je5Yi8hF2t3yMPU1Ypt3AXazg7mTlykOzVoTQuYBhW CsVROChkcvvzv0AklQ9owP8mk2hI9YlHTstwuFIEcjzIYJQWr0i7q2HnEx+4a6mlJtkp reJ8RqkdwzPXUVD61UczHX/f9RuZBkuqVYmRxL1y+9Txy2SnIQD5009Kpk6MZu01PNH7 Y1+2FDDKu2mfNkB6KOWJjbjw8Q7WMmLwY7VgvpT1JVaWfgpv0uxeEJWCHf+FvzQBmEkq FQuqWt6WU8RuQVyGVJNV5W1+d9WWYYF8F8WtBCAF3VjZaB6dzeGanuDTSOmAswCF9jHB gV9Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 32si19391965plc.427.2019.04.05.05.39.52; Fri, 05 Apr 2019 05:40:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728683AbfDEMjN (ORCPT + 99 others); Fri, 5 Apr 2019 08:39:13 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34542 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726027AbfDEMjM (ORCPT ); Fri, 5 Apr 2019 08:39:12 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C7AAA30027B5; Fri, 5 Apr 2019 12:39:12 +0000 (UTC) Received: from treble (ovpn-123-87.rdu2.redhat.com [10.10.123.87]) by smtp.corp.redhat.com (Postfix) with ESMTPS id EDAB55D71B; Fri, 5 Apr 2019 12:39:11 +0000 (UTC) Date: Fri, 5 Apr 2019 07:39:09 -0500 From: Josh Poimboeuf To: Luis Ressel Cc: Peter Zijlstra , open list , stable@vger.kernel.org Subject: Re: [PATCH] objtool: Don't use -Werror Message-ID: <20190405123909.tupbgueie4czg2dd@treble> References: <20190405110151.2461-1-aranea@aixah.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190405110151.2461-1-aranea@aixah.de> User-Agent: NeoMutt/20180716 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.43]); Fri, 05 Apr 2019 12:39:12 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 05, 2019 at 01:01:50PM +0200, Luis Ressel wrote: > -Werror can be handy for development, but enabling it for production > builds is a bad idea -- other compilers might produce unexpected > warnings, or #included library headers might trigger warnings. > > In my case, libelf's (not elfutil's!) headers trigger several -Wundef > warnings. This wasn't a problem before 056d28d135bc, since gcc doesn't > emit warnings for system headers, but now that there's a > -I/usr/include/libelf/ in the gcc command line, those warnings appear > and break the build. Hi Luis, What version of libelf are you using? AFAIK, the non-elfutils version of libelf is buggy and has been unmaintained for 10 years. > CC'ing stable@ since 056d28d135bc has also been included in stable > versions. > > Fixes: 056d28d135bc ("objtool: Query pkg-config for libelf location") > Signed-off-by: Luis Ressel > Cc: stable@vger.kernel.org > --- > tools/objtool/Makefile | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tools/objtool/Makefile b/tools/objtool/Makefile > index 53f8be0f4a1f..ad2c11a881db 100644 > --- a/tools/objtool/Makefile > +++ b/tools/objtool/Makefile > @@ -34,7 +34,7 @@ INCLUDES := -I$(srctree)/tools/include \ > -I$(srctree)/tools/arch/$(HOSTARCH)/include/uapi \ > -I$(srctree)/tools/objtool/arch/$(ARCH)/include > WARNINGS := $(EXTRA_WARNINGS) -Wno-switch-default -Wno-switch-enum -Wno-packed > -CFLAGS += -Werror $(WARNINGS) $(KBUILD_HOSTCFLAGS) -g $(INCLUDES) $(LIBELF_FLAGS) > +CFLAGS += $(WARNINGS) $(KBUILD_HOSTCFLAGS) -g $(INCLUDES) $(LIBELF_FLAGS) > LDFLAGS += $(LIBELF_LIBS) $(LIBSUBCMD) $(KBUILD_HOSTLDFLAGS) > > # Allow old libelf to be used: > -- > 2.21.0 > -- Josh