From: Luis Machado <luis.machado@linaro.org>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: Tom Tromey <tom@tromey.com>,
Sergio Durigan Junior <sergiodj@redhat.com>,
Tom de Vries <tdevries@suse.de>, Pedro Alves <palves@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Move gdbserver to top level
Date: Mon, 17 Feb 2020 14:29:00 -0000 [thread overview]
Message-ID: <95b5bb43-aa02-0dfd-76ec-c7da9e85a758@linaro.org> (raw)
In-Reply-To: <alpine.LFD.2.21.2002171407310.18621@redsun52.ssa.fujisawa.hgst.com>
On 2/17/20 11:21 AM, Maciej W. Rozycki wrote:
> On Mon, 17 Feb 2020, Luis Machado wrote:
>
>> Should --disable-gdb also imply --disable-gdbserver? Or should we be
>> able to build gdbserver without building gdb (sounds a bit more complex)?
>
> Nope, `--disable-gdb --enable-gdbserver' is typical for a cross-debug
> environment, where you want to configure and build cross-GDB with
> `--host=foo --target=bar' and `gdbserver' with `--host=bar'. Sometimes
> your build environment may not even be capable to build native GDB with
> `--host=bar', or your target system to run it, and in any case building
> GDB takes a lot of processing time compared to `gdbserver'. So it would
> be a waste of resources if we forced people to do that.
Well, that is a fair point. In which case i think we have a bug in our
hands.
>
> I build `gdbserver' by itself routinely, although I only did the minimum
> to convert from the old layout, that is rather than calling `configure'
> from gdb/gdbserver/ I now call it from gdbserver/. So far it has worked,
> although with the new arrangement it probably qualifies as a hack, and may
> stop working sometime.
>
> Maciej
>
next prev parent reply other threads:[~2020-02-17 14:29 UTC|newest]
Thread overview: 45+ 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
2020-01-26 16:01 ` Tom Tromey
2020-01-27 18:13 ` Pedro Alves
2020-01-28 0:37 ` Tom Tromey
2020-01-28 14:28 ` Pedro Alves
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 [this message]
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=95b5bb43-aa02-0dfd-76ec-c7da9e85a758@linaro.org \
--to=luis.machado@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@wdc.com \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.com \
--cc=tdevries@suse.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).