Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>,
	Alexander Richardson via Binutils <binutils@sourceware.org>
Cc: gdb-patches@sourceware.org,
	Alexander Richardson <Alexander.Richardson@cl.cam.ac.uk>
Subject: Re: [PATCH] GDB: Fix detection of ELF support when configuring with -Werror
Date: Sat, 28 Nov 2020 11:50:08 -0500	[thread overview]
Message-ID: <3f21122f-d27d-ede3-a99f-f58352832859@simark.ca> (raw)
In-Reply-To: <87r1oogh1n.fsf@tromey.com>

On 2020-11-20 10:54 a.m., Tom Tromey wrote:
>>>>>> "Alex" == Alexander Richardson via Binutils <binutils@sourceware.org> writes:
>
> Alex> I was configuring GDB with -Werror=implicit-function-definition in
> Alex> CFLAGS and the --disable-werror configure argument.
> Alex> I've dropped that flag from my build scripts for now, but I would like
> Alex> to add it again if this patch is accepted.
>
> It's kind of lame that we can't (AFAIK) specify one set of flags for
> configure and another set for the build itself.  Maybe this could be
> added to the top-level Makefile somehow.

I don't know, having multiple set of flags would make it even more
confusing I think.  And it would be risky to have configure take some
decisions based on some set of flags and compile the code using some
different set of flags.

Anyhow, I've pushed Alexander's patch, since it can't really hurt and
it fixes the problem for now.  I adjusted the commit message a bit to
mention explicitly that it was caused by -Wimplicit-function-declaration
(it's mentioned in the compiler error message, but I think it's good to
make it clear, in case someone tries to reproduce the problem).

Simon

      reply	other threads:[~2020-11-28 16:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11  9:20 Alex Richardson via Gdb-patches
2020-11-11 20:48 ` Simon Marchi
2020-11-12  9:25   ` Alexander Richardson via Gdb-patches
2020-11-12 14:23     ` Tom Tromey
2020-11-12 14:25     ` Simon Marchi
2020-11-13 12:09       ` Nick Clifton via Gdb-patches
2020-11-13 13:46         ` Simon Marchi
2020-11-20  1:12           ` Alexander Richardson via Gdb-patches
2020-11-20 15:54             ` Tom Tromey
2020-11-28 16:50               ` Simon Marchi [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=3f21122f-d27d-ede3-a99f-f58352832859@simark.ca \
    --to=simark@simark.ca \
    --cc=Alexander.Richardson@cl.cam.ac.uk \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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