[PATCH] Remove gdb/nlm subdirectory

[Steve Ellcey <sje@cup.hp.com>]

A few days ago I sent out a question about the gdb/nlm subdirectory to
the gdb mailing list and why it used autoconf 2.13 instead of autoconf
2.59 like the rest of gdb.  While it appears the subdirectory could be
updated it also looks like nobody is using it anymore and that it could
be removed from gdb.

So here is a patch to remove the gdb/nlm subdirectory.  I don't have a
netware platform on which to test this, but I did test it on a couple of
other platforms just to make sure my changes didn't break configure or
make in general.

What do people think?  Does one of the maintainers want to approve this
patch?

Steve Ellcey
sje@cup.hp.com



gdb/ChangeLog

2006-03-23  Steve Ellcey  <sje@cup.hp.com>

	* Makefile.in (nlm): Remove target.
	* configure.tgt (i[34567]86-*-netware*): Do not set build_nlm.
	* configure.ac: Remove AC_CONFIG_SUBDIRS of nlm.
	* configure: Regenerate.
	* doc/gdb.texinfo: Remove gdbserve.nlm documentation.
	* nlm: Remove directory.


*** Makefile.in.orig	Thu Mar 23 10:49:41 2006
--- Makefile.in	Thu Mar 23 10:50:00 2006
*************** $(TUI)$(EXEEXT): tui-main.o libgdb.a $(A
*** 1202,1210 ****
  		-o $(TUI)$(EXEEXT) tui-main.o libgdb.a \
  		$(TDEPLIBS) $(TUI_LIBRARY) $(CLIBS) $(LOADLIBES)
  
- nlm:	force
- 	rootme=`pwd`; export rootme; $(MAKE) $(TARGET_FLAGS_TO_PASS) DO=all DODIRS=nlm subdir_do
- 
  # Create a library of the gdb object files and build GDB by linking
  # against that.
  #
--- 1202,1207 ----
*** configure.ac.orig	Tue Feb 21 13:02:25 2006
--- configure.ac	Thu Mar 23 10:50:26 2006
*************** if test "x$target" = "x$host"; then
*** 1513,1524 ****
    fi
  fi
  
- # We configure the nlm subdirectory on netware targets, as instructed
- # by configure.tgt.
- if test "x$build_nlm" = xyes; then
-    AC_CONFIG_SUBDIRS(nlm)
- fi
- 
  # If hostfile (XM_FILE) and/or targetfile (DEPRECATED_TM_FILE) and/or
  # nativefile (NAT_FILE) is not set in config/*/*.m[ht] files, we link
  # to an empty version.
--- 1513,1518 ----
*** configure.tgt.orig	Thu Mar 23 10:50:51 2006
--- configure.tgt	Thu Mar 23 10:51:15 2006
*************** i[34567]86-*-linux*)	gdb_target=linux
*** 96,104 ****
  			build_gdbserver=yes
  			;;
  i[34567]86-*-gnu*)	gdb_target=i386gnu ;;
! i[34567]86-*-netware*)	gdb_target=i386
! 			build_nlm=yes
! 			;;
  i[34567]86-*-cygwin*)	gdb_target=cygwin  ;;
  i[34567]86-*-*)		gdb_target=i386 ;;
  
--- 96,102 ----
  			build_gdbserver=yes
  			;;
  i[34567]86-*-gnu*)	gdb_target=i386gnu ;;
! i[34567]86-*-netware*)	gdb_target=i386 ;;
  i[34567]86-*-cygwin*)	gdb_target=cygwin  ;;
  i[34567]86-*-*)		gdb_target=i386 ;;
  
*** doc/gdb.texinfo.orig	Thu Mar 23 11:09:44 2006
--- doc/gdb.texinfo	Thu Mar 23 11:10:25 2006
*************** want to try.
*** 12139,12145 ****
  @menu
  * Connecting::                  Connecting to a remote target
  * Server::	                Using the gdbserver program
- * NetWare::                     Using the gdbserve.nlm program
  * Remote configuration::        Remote configuration
  * remote stub::                 Implementing a remote stub
  @end menu
--- 12139,12144 ----
*************** you normally would), do that with the @c
*** 12393,12443 ****
  it @emph{before} connecting to the server; otherwise, you will get an
  error message saying @code{"Program is already running"}, since the
  program is considered running after the connection.
- 
- @end table
- 
- @node NetWare
- @section Using the @code{gdbserve.nlm} program
- 
- @kindex gdbserve.nlm
- @code{gdbserve.nlm} is a control program for NetWare systems, which
- allows you to connect your program with a remote @value{GDBN} via
- @code{target remote}.
- 
- @value{GDBN} and @code{gdbserve.nlm} communicate via a serial line,
- using the standard @value{GDBN} remote serial protocol.
- 
- @table @emph
- @item On the target machine,
- you need to have a copy of the program you want to debug.
- @code{gdbserve.nlm} does not need your program's symbol table, so you
- can strip the program if necessary to save space.  @value{GDBN} on the
- host system does all the symbol handling.
- 
- To use the server, you must tell it how to communicate with
- @value{GDBN}; the name of your program; and the arguments for your
- program.  The syntax is:
- 
- @smallexample
- load gdbserve [ BOARD=@var{board} ] [ PORT=@var{port} ]
-               [ BAUD=@var{baud} ] @var{program} [ @var{args} @dots{} ]
- @end smallexample
- 
- @var{board} and @var{port} specify the serial line; @var{baud} specifies
- the baud rate used by the connection.  @var{port} and @var{node} default
- to 0, @var{baud} defaults to 9600@dmn{bps}.
- 
- For example, to debug Emacs with the argument @samp{foo.txt}and
- communicate with @value{GDBN} over serial port number 2 or board 1
- using a 19200@dmn{bps} connection:
- 
- @smallexample
- load gdbserve BOARD=1 PORT=2 BAUD=19200 emacs foo.txt
- @end smallexample
- 
- @item
- On the @value{GDBN} host machine, connect to your target (@pxref{Connecting,,
- Connecting to a remote target}).
  
  @end table
  
--- 12392,12397 ----