libstdc++.exp (libstdc++_init): Set $GCC_COLORS="" instead of insisting that GCC understand...

2014-07-11  Samuel Bronson  <naesten@gmail.com>

	* testsuite/lib/libstdc++.exp  (libstdc++_init): Set $GCC_COLORS=""
	instead of insisting that GCC understand -fdiagnostics-color=never

From-SVN: r212458

libstdc++-v3/ChangeLog

 2014-07-11  Samuel Bronson  <naesten@gmail.com>
+
+	* testsuite/lib/libstdc++.exp  (libstdc++_init): Set $GCC_COLORS=""
+	instead of insisting that GCC understand -fdiagnostics-color=never
+
+2014-07-11  Samuel Bronson  <naesten@gmail.com>
 	    Matthias Klose  <doko@ubuntu.com>
 
 	PR libstdc++/58962

libstdc++-v3/testsuite/lib/libstdc++.exp

@@ -289,9 +289,11 @@ proc libstdc++_init { testfile } {
 
     v3track cxxflags 2
 
+    # Should be as good as -fdiagnostics-color=never, but more compatible
+    setenv GCC_COLORS ""
     # Always use MO files built by this test harness.
-    set cxxflags "-fdiagnostics-color=never $cxxflags -DLOCALEDIR=\".\""
     set ccflags "$cxxflags -DLOCALEDIR=\".\""
+    set cxxflags "$cxxflags -DLOCALEDIR=\".\""
 
     # If a PCH file is available, use it.  We must delay performing
     # this check until $cxx and such have been initialized because we