Make testing gdb with FORCE_SEPARATE_MI_TTY=1 actually work

Runing the whole gdb testsuite with MI on a separate tty, with:

  make check RUNTESTFLAGS="FORCE_SEPARATE_MI_TTY=1"

Doesn't actually work because commit 51f77c3704a6 ("Add testing
infrastruture bits for running with MI on a separate UI") included a
last-minute rename typo, now fixed with this commit.

gdb/testsuite/ChangeLog:
2016-06-30  Pedro Alves  <palves@redhat.com>

	* lib/mi-support.exp (default_mi_gdb_start): Declare global
	FORCE_SEPARATE_MI_TTY, not SEPARATE_MI_TTY.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 5dd926e..ab0d9e6 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,8 @@
+2016-06-30  Pedro Alves  <palves@redhat.com>
+
+       * lib/mi-support.exp (default_mi_gdb_start): Declare global
+       FORCE_SEPARATE_MI_TTY, not SEPARATE_MI_TTY.
+
 2016-06-29  Yao Qi  <yao.qi@linaro.org>
 
        * gdb.base/return.c: Add copyright header.

diff --git a/gdb/testsuite/lib/mi-support.exp b/gdb/testsuite/lib/mi-support.exp
index 7b5c90b..28af70a 100644 (file)
--- a/gdb/testsuite/lib/mi-support.exp
+++ b/gdb/testsuite/lib/mi-support.exp
@@ -193,7 +193,7 @@ proc default_mi_gdb_start { args } {
     global timeout
     global gdb_spawn_id gdb_main_spawn_id inferior_spawn_id mi_spawn_id
     global MIFLAGS
-    global SEPARATE_MI_TTY
+    global FORCE_SEPARATE_MI_TTY
 
     if {[info exists FORCE_SEPARATE_MI_TTY]} {
        set separate_mi_pty $FORCE_SEPARATE_MI_TTY