public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Discussion <gdb@sourceware.cygnus.com>
Subject: Obsolete systems for GDB 5.1?
Date: Wed, 17 Jan 2001 20:24:00 -0000	[thread overview]
Message-ID: <3A666F6F.90372D25@cygnus.com> (raw)

I'd like to table the following as candidates for removal from GDB. 
They would be marked as obsolete in GDB 5.1.


The following systems were identified because they continue to use the
*xdep.c* file.

Rather than fix these platforms, I'd like to remove them.  Eliminating
*xdep.c from GDB should greatly simplify things like the move to
automake (and more immediatly the long outstanding need to fix
gdb/gdbserv's configury).

	m68030-sony-*)		gdb_host=news1000 ;;
	m68*-isi-*)		gdb_host=isi ;;
	m68*-sony-*)		gdb_host=news ;;
	a29k-*-*)		gdb_host=ultra3 ;;
	ns32k-umax-*)		gdb_host=umax ;;
	mpw*-*-*)		see mpw-config.in


The following systems were identified because they they do not have a
maintainer and are known to not build:

	i[3456]86-*-sunos*)	gdb_host=sun386 ;;  (This is *NOT* solaris-2)
	ns32k-umax-*)		gdb_host=umax ;;
		Uses deleted function safe_strsignal().


The following systems were identified because their target does not have
a maintainer *AND* I was not able to build them (FreeBSD host).  The
file gdb/MAINTAINERS will contain up-to-date status on this and other
targets.

	i960
	mcore
	mn10200
	ns32k
		ns32k-*-mach3*)		gdb_host=ns32km3 ;;
		ns32k-*-netbsd*)	gdb_host=nbsd ;;
		ns32k-umax-*)		gdb_host=umax ;;
		ns32k-utek-sysv*)	gdb_host=merlin ;;
	tic80
	v850
	w65
	z8k

Comments.  Suggestions and rejections.

	Andrew

             reply	other threads:[~2001-01-17 20:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-17 20:24 Andrew Cagney [this message]
2001-01-17 20:28 ` Christopher Faylor
2001-01-18 13:53 ` J.T. Conklin
2001-01-18 14:40 ` Jonathan Larmour
2001-01-18 14:40 ` J.T. Conklin
2001-01-18 22:21 ` Andrew Cagney
2001-01-25 13:37 ` Mark Kettenis

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=3A666F6F.90372D25@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb@sourceware.cygnus.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).