Disable gdbserver on host != target configurations
authorMaciej W. Rozycki <macro@wdc.com>
Wed, 12 Feb 2020 13:50:30 +0000 (13:50 +0000)
committerPedro Alves <palves@redhat.com>
Wed, 12 Feb 2020 13:50:30 +0000 (13:50 +0000)
commitf20e3e823d56e54ffe56792ea6a2fe947c2dec0d
tree41cec8f5e99972f8ed02ac0071155d5d52b7dc30
parent38de8abe21fe17c31888094bd860a84f88cb5749
Disable gdbserver on host != target configurations

Correct fallout from commit 919adfe84092 ("Move gdbserver to top level")
and revert to not building `gdbserver' in a cross-configuration, that is
where host != target, matching the documented behaviour.  We have no way
to support non-native `gdbserver', and native `gdbserver' is usually of
no use with cross-GDB of the chosen host.

gdbserver/ChangeLog:
2020-02-12  Maciej W. Rozycki <macro@wdc.com>
    Pedro Alves  <palves@redhat.com>

Skip building gdbserver in a cross-configuration.
* configure.srv: Set $gdbserver_host depending on whether $target
is $host.  Use $gdbserver_host instead of $host.
gdbserver/ChangeLog
gdbserver/configure.srv