[PATCH] Correct DJGPP-related bitrot

[Eli Zaretskii <eliz@is.elta.co.il>]

Looks like the DJGPP port suffered some bitrot while I was looking the 
other way.  FYI, I've just commited the changes below to fix that.


2001-06-04  Eli Zaretskii  <eliz@is.elta.co.il>

	* go32-nat.c (go32_wait): Change the return value to ptid_t.

	* config/djgpp/fnchange.lst: Add two new files in the
	gdb/testsuite/gdb.c++/ directory.

	* config/djgpp/djconfig.sh (lt_cv_sys_max_cmd_len): Set to 12KB.


--- gdb/go32-nat.c~0	Sat Jun  2 20:34:58 2001
+++ gdb/go32-nat.c	Sat Jun  2 20:34:00 2001
@@ -340,7 +340,7 @@ go32_resume (ptid_t ptid, int step, enum
 
 static char child_cwd[FILENAME_MAX];
 
-static int
+static ptid_t
 go32_wait (ptid_t ptid, struct target_waitstatus *status)
 {
   int i;
@@ -455,7 +455,7 @@ go32_wait (ptid_t ptid, struct target_wa
 	    }
 	}
     }
-  return SOME_PID;
+  return pid_to_ptid (SOME_PID);
 }
 
 static void


--- gdb/config/djgpp/fnchange.l~0	Thu May  3 16:25:20 2001
+++ gdb/config/djgpp/fnchange.lst	Sat Jun  2 19:46:30 2001
@@ -177,6 +177,8 @@
 @V@/gdb/testsuite/gdb.c++/method.exp @V@/gdb/testsuite/gdb.cxx/method.exp
 @V@/gdb/testsuite/gdb.c++/misc.cc @V@/gdb/testsuite/gdb.cxx/misc.cc
 @V@/gdb/testsuite/gdb.c++/misc.exp @V@/gdb/testsuite/gdb.cxx/misc.exp
+@V@/gdb/testsuite/gdb.c++/namespace.cc @V@/gdb/testsuite/gdb.cxx/namespace.cc
+@V@/gdb/testsuite/gdb.c++/namespace.exp @V@/gdb/testsuite/gdb.cxx/namespace.exp
 @V@/gdb/testsuite/gdb.c++/overload.cc @V@/gdb/testsuite/gdb.cxx/overload.cc
 @V@/gdb/testsuite/gdb.c++/overload.exp @V@/gdb/testsuite/gdb.cxx/overload.exp
 @V@/gdb/testsuite/gdb.c++/ovldbreak.cc @V@/gdb/testsuite/gdb.cxx/ovldbreak.cc


--- gdb/config/djgpp/djconfig.s~0	Mon Mar 26 13:26:44 2001
+++ gdb/config/djgpp/djconfig.sh	Sat Jun  2 19:43:36 2001
@@ -126,6 +126,12 @@
 # Define explicitly the .exe extension because on W95 with LFN=y
 # the check might fail
 export am_cv_exeext=.exe
+# ltconfig wants to compute the maximum command-line length, but
+# Bash 2.04 doesn't like that (it doesn't have any limit ;-), and
+# reboots the system.  We know our limit in advance, so we don't
+# need all that crap.  Assuming that the environment size is less
+# than 4KB, we can afford 12KB of command-line arguments.
+export lt_cv_sys_max_cmd_len=12288
 
 # The configure script needs to see the `install-sh' script, otherwise
 # it decides the source installation is broken.  But "make install" will