depcomp tests: avoid spurious failures with 'dashXmstdout' depmode

* tests/gen-testsuite-part: The 'dashXmstdout' depmode cannot be
truly forced on gcc (like we were trying to do, causing spurious
failures in the process); so don't do that.  This change shouldn't
actually reduce coverage anyway, since, as the comments in
'lib/depcomp' say, the 'dashXmstdout' depmode is just like
the 'dashmstdout' one, only with a different argument for the
compiler.

diff --git a/tests/gen-testsuite-part b/tests/gen-testsuite-part
index ad00657827ffa790e468e75af392f077ea4af798..195d6f59a8b6e229fb8c2b1531fa5e2da33ec760 100755 (executable)
--- a/tests/gen-testsuite-part
+++ b/tests/gen-testsuite-part
@@ -3,7 +3,7 @@
 # of the Automake testsuite.  Also, automatically generate some more
 # tests from them (for particular cases/setups only).
 
-# Copyright (C) 2011 Free Software Foundation, Inc.
+# Copyright (C) 2011, 2012 Free Software Foundation, Inc.
 
 # This program is free software; you can redistribute it and/or modify
 # it under the terms of the GNU General Public License as published by
@@ -327,7 +327,6 @@ my %depmodes =
     disabled     => ["cc"],
     makedepend   => ["cc", "makedepend"],
     dashmstdout  => ["gcc"],
-    dashXmstdout => ["gcc"],
     cpp          => ["gcc"],
 # This is for older (pre-3.x) GCC versions.  Newer versions
 # have depmode "gcc3".