Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Move gdbserver to top level
Date: Sat, 25 Jan 2020 16:55:00 -0000	[thread overview]
Message-ID: <171a3144-af37-1c29-a2a4-c4cd7eaa14c0@redhat.com> (raw)
In-Reply-To: <874kwk8nz9.fsf@tromey.com>

On 1/24/20 10:54 PM, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
> 
> Pedro> This should really be done by sourcing a file in gdbserver/
> Pedro> If we do that, then the info about whether a system supports
> Pedro> gdbserver is contained under gdbserver/, and does not
> Pedro> require syncing with gcc whenever is changes.
> 
> Good idea, I've made this change.  Here's an updated patch.
> 
> As before, I've removed the generated files.
> 
> If you want to test it, it is in submit/move-gdbserver-to-top on my
> github.

Thanks!  I poked at it a bit.  I think this looks good, though I
have a comment on the dependencies below.

I think this should have a NEWS entry, given that it affects
people building standalone gdbserver today.  Do you have
documentation changes queued?

>  2020-01-19  Simon Marchi  <simon.marchi@polymtl.ca>
>  
>  	* remote-sim.c (gdbsim_target::wait): Return
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 805f2e3ac43..5b8a4efbdf6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -41,7 +41,7 @@ config.guess; config.sub; readline/support/config.{sub,guess}
>  depcomp; mkinstalldirs
>          Send bug reports and patches to bug-automake@gnu.org.
>  
> -gdb/; gdbsupport/; gnulib/; readline/; sim/; GDB's part of include/
> +gdb/; gdbserver/; gdbsupport/; gnulib/; readline/; sim/; GDB's part of include/
>  	GDB: http://www.gnu.org/software/gdb/
>  	Patches to gdb-patches@sourceware.org.
>  	See also gdb/MAINTAINERS and sim/MAINTAINERS.
> diff --git a/Makefile.def b/Makefile.def
> index 253eb45ef14..de35083d81e 100644
> --- a/Makefile.def
> +++ b/Makefile.def
> @@ -114,6 +114,7 @@ host_modules= { module= zlib; no_install=true; no_check=true;
>  	        extra_configure_flags='@extra_host_zlib_configure_flags@';};
>  host_modules= { module= gnulib; };
>  host_modules= { module= gdbsupport; };
> +host_modules= { module= gdbserver; };
>  host_modules= { module= gdb; };
>  host_modules= { module= expect; };
>  host_modules= { module= guile; };
> @@ -409,6 +410,12 @@ dependencies = { module=all-gdb; on=all-libdecnumber; };
>  dependencies = { module=all-gdb; on=all-libtermcap; };
>  dependencies = { module=all-gdb; on=all-libctf; };
>  
> +// Host modules specific to gdbserver.
> +dependencies = { module=configure-gdbserver; on=all-intl; };

This surprised me, as I don't think gdbserver actually depends on
intl currently?  Might still be a good idea to actually enable it,
but I was surprised from an "as pure as possible" perspective.

> +// Depend on all-libiconv so that configure checks for iconv
> +// functions will work.
> +dependencies = { module=configure-gdbserver; on=all-libiconv; };
> +

Likewise curious.  Can you clarify where the configure checks
come from?

Locally I removed the intl and iconv dependencies and the
resulting gdbserver (w/ make all-gdbserver) was identical byte
for byte for me.

Thanks,
Pedro Alves


  reply	other threads:[~2020-01-25 16:50 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 20:07 Tom Tromey
2020-01-21  5:34 ` Simon Marchi
2020-01-23 22:03   ` Tom Tromey
2020-01-24 14:29     ` Hannes Domani via gdb-patches
2020-01-24 15:12       ` Tom Tromey
2020-01-24 15:57         ` Tom Tromey
2020-01-24 16:02           ` Hannes Domani via gdb-patches
2020-01-24 16:28             ` Tom Tromey
2020-01-24 16:35               ` Hannes Domani via gdb-patches
2020-01-24 19:03                 ` Hannes Domani via gdb-patches
2020-01-24 15:23 ` Pedro Alves
2020-01-25  0:07   ` Tom Tromey
2020-01-25 16:55     ` Pedro Alves [this message]
2020-01-26 16:01       ` Tom Tromey
2020-01-27 18:13         ` Pedro Alves
2020-01-28  0:37           ` Tom Tromey
2020-02-03 21:34             ` Tom Tromey
2020-02-07 16:06               ` Simon Marchi
2020-02-09 13:59               ` Tom de Vries
2020-02-09 14:17                 ` Tom de Vries
2020-02-10 10:01                   ` Tom de Vries
2020-02-10 15:54                     ` Sergio Durigan Junior
2020-02-12  0:55                       ` Tom Tromey
2020-02-12 16:47                         ` Sergio Durigan Junior
2020-02-14  3:54                         ` Sergio Durigan Junior
2020-02-14 18:43                           ` Tom Tromey
2020-02-14 21:14                             ` Tom Tromey
2020-02-17 13:58                               ` Luis Machado
2020-02-17 14:21                                 ` Maciej W. Rozycki
2020-02-17 14:29                                   ` Luis Machado
2020-02-17 16:57                                 ` Luis Machado
2020-02-17 17:01                                 ` Tom Tromey
2020-02-17 17:28                                   ` Aktemur, Tankut Baris
2020-02-17 18:46                                     ` Tom Tromey
2020-02-10 10:59                   ` [PATCH][gdb/testsuite] Skip multi-target.exp without gdbserver Tom de Vries
2020-02-10 12:20                     ` Pedro Alves
2020-02-09 23:05               ` [PATCH] Move gdbserver to top level Alan Modra
2020-02-10 12:02                 ` Pedro Alves
2020-02-10  9:52               ` Andreas Schwab
2020-02-10 12:13                 ` Pedro Alves
2020-02-10 13:04                   ` Andreas Schwab
2020-02-10 13:15                   ` Andreas Schwab
2020-02-11 13:48                     ` [PATCH] Disable gdbserver on host != target configurations (Re: [PATCH] Move gdbserver to top level) Pedro Alves
2020-02-11 15:29                       ` Tom Tromey

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=171a3144-af37-1c29-a2a4-c4cd7eaa14c0@redhat.com \
    --to=palves@redhat.com \
    --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