From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Move gdbserver to top level
Date: Fri, 24 Jan 2020 15:23:00 -0000 [thread overview]
Message-ID: <7ceebbb7-b2f7-3d4a-1d8a-f31310badbe8@redhat.com> (raw)
In-Reply-To: <87d0bf45up.fsf@tromey.com>
On 1/19/20 7:13 PM, Tom Tromey wrote:
>
> +# Only allow gdbserver on some systems.
> +build_gdbserver=
> +case "$host" in
> +aarch64*-*-linux*)
> + # Target: AArch64 linux
> + build_gdbserver=yes
> + ;;
> +
> +arm*-wince-pe | arm*-*-mingw32ce*)
> + # Target: ARM based machine running Windows CE (win32)
> + build_gdbserver=yes
> + ;;
> +arm*-*-linux*)
> + # Target: ARM based machine running GNU/Linux
> + build_gdbserver=yes
> + ;;
> +bfin-*-*linux*)
> + # Target: Blackfin Linux
> + gdb_target_obs="bfin-tdep.o bfin-linux-tdep.o linux-tdep.o"
> + build_gdbserver=yes
> + ;;
> +i[34567]86-*-nto*)
> + # Target: Intel 386 running qnx6.
> + build_gdbserver=yes
> + ;;
> +i[34567]86-*-linux*)
> + # Target: Intel 386 running GNU/Linux
> + build_gdbserver=yes
> + ;;
> +i[34567]86-*-cygwin*)
> + # Target: Intel 386 running win32
> + build_gdbserver=yes
> + ;;
> +i[34567]86-*-mingw32*)
> + # Target: Intel 386 running win32
> + build_gdbserver=yes
> + ;;
> +ia64-*-linux*)
> + # Target: Intel IA-64 running GNU/Linux
> + build_gdbserver=yes
> + ;;
> +m32r*-*-linux*)
> + # Target: Renesas M32R running GNU/Linux
> + build_gdbserver=yes
> + ;;
> +m68*-*-linux*)
> + # Target: Motorola m68k with a.out and ELF
> + build_gdbserver=yes
> + ;;
> +mips*-*-linux*)
> + # Target: Linux/MIPS
> + build_gdbserver=yes
> + ;;
> +or1k*-*-linux*)
> + # Target: OpenCores OpenRISC 1000 32-bit running Linux
> + build_gdbserver=yes
> + ;;
> +
> +powerpc*-*-linux*)
> + # Target: PowerPC running Linux
> + build_gdbserver=yes
> + ;;
> +s390*-*-linux*)
> + # Target: S390 running Linux
> + build_gdbserver=yes
> + ;;
> +score-*-*)
> + # Target: S+core embedded system
> + build_gdbserver=yes
> + ;;
> +sh*-*-linux*)
> + # Target: GNU/Linux Super-H
> + build_gdbserver=yes
> + ;;
> +sparc-*-linux*)
> + # Target: GNU/Linux SPARC
> + build_gdbserver=yes
> + ;;
> +sparc64-*-linux*)
> + # Target: GNU/Linux UltraSPARC
> + build_gdbserver=yes
> + ;;
> +tilegx-*-linux*)
> + # Target: TILE-Gx
> + build_gdbserver=yes
> + ;;
> +x86_64-*-linux*)
> + # Target: GNU/Linux x86-64
> + build_gdbserver=yes
> + ;;
> +x86_64-*-mingw* | x86_64-*-cygwin*)
> + # Target: MingW/amd64
> + build_gdbserver=yes
> + ;;
> +xtensa*-*-*linux*)
> + # Target: GNU/Linux Xtensa
> + build_gdbserver=yes
> + ;;
> +esac
> +
> +if test "x$build_gdbserver" = x; then
> + noconfigdirs="$noconfigdirs gdbserver"
> +fi
This should really be done by sourcing a file in gdbserver/
If we do that, then the info about whether a system supports
gdbserver is contained under gdbserver/, and does not
require syncing with gcc whenever is changes.
See the section starting at:
# Disable libatomic on unsupported systems.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2020-01-24 15:23 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 [this message]
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-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=7ceebbb7-b2f7-3d4a-1d8a-f31310badbe8@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