public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH] config: Pass the compiler -Werror during warning detection
Date: Tue, 03 May 2016 11:04:31 +0200	[thread overview]
Message-ID: <1462266271.7999.44.camel@redhat.com> (raw)
In-Reply-To: CADU+-uCphgG2sidR8szkcLKiMniqydijs5h=skv7+j1Uy4zDUQ@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]

On Mon, 2016-05-02 at 14:46 -0700, Filipe Brandenburger wrote:
> On Mon, May 2, 2016 at 2:21 PM, Mark Wielaard <mjw@redhat.com> wrote:
> > I am not against this patch if it makes our compiler feature detection
> > better.
> 
> I'd say it makes configure closer to build, considering during build
> time the Makefile is already adding -Werror to most targets.
> Furthermore, the check for -Wlogical-op was already using -Werror as
> well, so I don't see why not have the three others be consistent with
> it (granted, the -Wlogical-op one actually uses non-trivial code,
> while the others just compile a trivial file.)

That makes sense. The -Wlogical-op one was special because we didn't
just want to check that the warning flag was supported, but also that it
didn't produce false positives, which happened with older GCC releases.

> Right now I have to "trick" configure into skipping that test, with:
> 
>   $ ./configure CC=clang-3.5 ac_cv_c99=yes
> 
> And then the build works, at least of libelf/ subdir.
> 
> I hope you agree with my arguments on consistency (-Werror at
> configure vs. build time), but if you feel strongly against this patch
> we do have some possible workarounds (such as passing -Werror in
> CFLAGS of ./configure).

The patch is fine. Pushed it to master.
Just wanted to double check the changes/improvements were deliberate.

Thanks,

Mark

             reply	other threads:[~2016-05-03  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03  9:04 Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-05-02 21:46 Filipe Brandenburger
2016-05-02 21:21 Mark Wielaard
2016-05-02 20:26 Filipe Brandenburger

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=1462266271.7999.44.camel@redhat.com \
    --to=mjw@redhat.com \
    --cc=elfutils-devel@lists.fedorahosted.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 read-only IMAP folder(s) and NNTP newsgroup(s).