Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simark@simark.ca>, Tom Tromey <tom@tromey.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH v2 0/6] Move gdbsupport to top level
Date: Fri, 17 Jan 2020 15:32:00 -0000	[thread overview]
Message-ID: <6b0b7f90-f526-73a9-3de8-aea958688d15@redhat.com> (raw)
In-Reply-To: <2cb89dd1-f029-d495-4823-72ae2d5253d2@simark.ca>

On 1/17/20 2:10 PM, Simon Marchi wrote:
> On 2020-01-17 8:35 a.m., Pedro Alves wrote:
>>>> So the original solution of adding the gnulib dir to the include path
>>>> isn't that bad, though I call it a hack.
>>>
>>> I would have to see it, but it sounds like the simplest solution.
>>
>> It was the first patch I posted, here:
>>  https://sourceware.org/ml/gdb-patches/2020-01/msg00419.html
> 
> Ok thanks, I did not follow this story from the beginning.
> 
>> But, gosh makes me realize there's an even simpler solution...
>> Just rename support-config.h to config.h...  Do we need to call
>> it something else for some reason?  I couldn't find one.
> 
> That's a good idea.
> 
>>>
>>>>> The gdb-config.h above should be gdbserver-config.h.
>>>> Here's v2.  WDYT?  Which of all the approaches discussed would
>>>> you prefer?
>>>
>>> Probably the solution that involves the least files and indirections.  But
>>> the one proposed in the latest patch is fine with me too.  It's set and
>>> forget, once it builds again we won't think about it, at least until the
>>> next time it breaks.
>>
>> Note that we already kind of have the config.h indirections via common-defs.h,
>> where we include the multiple config.h files.  This just moves those
>> indirections to the file actually named config.h.
>>
>>> The buildbot is struggling with this (sending many breakage emails), so I
>>> think you should choose one and push it.  Then we can cancel all the builds
>>> on the master branch until that commit.
>>
>> Anyway, here's the simpler patch...    Let's call it approach #3.
>>
>> Approach #1 - add -Ignulib
>> Approach #2 - add wrapper config.h files in the source dirs
>> Approach #3 - rename support-config.h -> config.h
> 
> I'd say let's go for #3, since that's how gdb and gdbserver already work,
> it's been working well for years, so it's proven already.

I've merged #3 now.  We discussed adding a comment to
gdbsupport/Makefile.am about the order of include paths, but it
turns out that the -I. is added by automake by default
(DEFAULT_INCLUDES), not explicitly set.  gdb and gdbserver's
Makefile.in have comments about it already.  So I applied the
patch as it was.

Thanks,
Pedro Alves


  reply	other threads:[~2020-01-17 15:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09  0:58 Tom Tromey
2020-01-09  0:58 ` [PATCH v2 4/6] Remove use of <config.h> from gdb/nat/ Tom Tromey
2020-01-09  0:58 ` [PATCH v2 1/6] Consolidate definition of USE_WIN32API Tom Tromey
2020-01-09  0:58 ` [PATCH v2 5/6] Add gdbsupport check-defines script Tom Tromey
2020-01-09  0:58 ` [PATCH v2 6/6] Don't link gdb twice against libiberty Tom Tromey
2020-01-11 16:58 ` [PATCH v2 0/6] Move gdbsupport to top level Tom Tromey
2020-01-12  2:48   ` Simon Marchi
2020-01-14 23:25     ` Tom Tromey
2020-01-15  0:36     ` Tom Tromey
2020-01-15 21:27   ` Christian Biesinger via gdb-patches
2020-01-17 18:02     ` Tom Tromey
2020-01-15 14:30 ` Pedro Alves
     [not found]   ` <8a8de6a9-37b8-cad3-c818-be903037fe48@redhat.com>
2020-01-15 16:07     ` Pedro Alves
     [not found]       ` <87c733a2-2b25-a954-88a1-9bfb1a7eca12@redhat.com>
2020-01-15 21:46         ` Pedro Alves
2020-01-15 22:12           ` Pedro Alves
2020-01-16  0:48             ` Pedro Alves
2020-01-16  2:57               ` Christian Biesinger via gdb-patches
2020-01-16 17:22                 ` Pedro Alves
2020-01-16 18:01                   ` Christian Biesinger via gdb-patches
2020-01-16 18:28                     ` Pedro Alves
2020-01-16 19:21                       ` Christian Biesinger via gdb-patches
2020-01-16  9:02           ` Simon Marchi
2020-01-16 15:24             ` Pedro Alves
2020-01-17 12:20               ` Simon Marchi
2020-01-17 13:37                 ` Pedro Alves
2020-01-17 14:40                   ` Simon Marchi
2020-01-17 15:32                     ` Pedro Alves [this message]
2020-01-17 18:13                       ` Tom Tromey
2020-01-16  4:23 ` 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=6b0b7f90-f526-73a9-3de8-aea958688d15@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --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