Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Alexander Richardson via Gdb-patches <gdb-patches@sourceware.org>
Cc: simark@simark.ca,
	Alexander Richardson <Alexander.Richardson@cl.cam.ac.uk>
Subject: Re: [PATCH] GDB: Fix detection of ELF support when configuring with -Werror
Date: Thu, 12 Nov 2020 07:23:30 -0700	[thread overview]
Message-ID: <878sb6fycd.fsf@tromey.com> (raw)
In-Reply-To: <CAEeofcjsWq7EVmRD8_vAm127X4Tj3MQF0c4xLj+HhU3ziSi5fg@mail.gmail.com> (Alexander Richardson via Gdb-patches's message of "Thu, 12 Nov 2020 09:25:29 +0000")

>>>>> "Alexander" == Alexander Richardson via Gdb-patches <gdb-patches@sourceware.org> writes:

Alexander> that's what I originally planned, but it seems like elf-bfd.h (and the
Alexander> headers it includes) don't include any system headers. Since I'm not
Alexander> familiar with any of this code I assumed this was intentional.

It seems like a question for the binutils list.

Maybe the answer is that configuring with -Werror shouldn't be done,
though.  I don't know the current state, but in the past, Autoconf
sometimes generated somewhat questionable test programs, so it's not
clear to me that the parts of configure that are out of gdb's control
are -Werror-clean.

Tom

  reply	other threads:[~2020-11-12 14:23 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 [this message]
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

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=878sb6fycd.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=Alexander.Richardson@cl.cam.ac.uk \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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