From: Tom Tromey <tom@tromey.com>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: gcc-patches@gcc.gnu.org, Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH] configure: Re-disable building cross-gdbserver
Date: Tue, 11 Feb 2020 15:24:00 -0000 [thread overview]
Message-ID: <87a75p9mg9.fsf@tromey.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2002081532520.18621@redsun52.ssa.fujisawa.hgst.com> (Maciej W. Rozycki's message of "Sat, 8 Feb 2020 16:21:12 +0000 (GMT)")
>>>>> "Maciej" == Maciej W Rozycki <macro@wdc.com> writes:
Maciej> Correct fallout from commit 919adfe84092 ("Move gdbserver to top level")
Maciej> and revert to not building `gdbserver' in a cross-configuration, that is
Maciej> where host != target, matching the documented behaviour. We have no way
Maciej> to support non-native `gdbserver', and native `gdbserver' is usually of
Maciej> no use with cross-GDB of the chosen host.
Pedro had a different way to do this, that keeps the decision under
gdbserver's control:
https://sourceware.org/ml/gdb-patches/2020-02/msg00383.html
Also note that I haven't sent the top-level configury patches upstream
to gcc yet. I am going to do this all at once, at the end. I think
there's one more patch that will be needed, once gdbserver depends on
the top-level gdbsupport.
Tom
next prev parent reply other threads:[~2020-02-11 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 16:21 Maciej W. Rozycki
2020-02-11 15:24 ` Tom Tromey [this message]
2020-02-11 21:02 ` Maciej W. Rozycki
2020-02-12 13:56 ` Pedro Alves
2020-02-13 23:48 ` Maciej W. Rozycki
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=87a75p9mg9.fsf@tromey.com \
--to=tom@tromey.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@wdc.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).