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
This commit is contained in:
Samuel Bronson 2014-07-11 15:32:14 +00:00 committed by Jonathan Wakely
parent c786fca61b
commit 7cd41cda09
2 changed files with 8 additions and 1 deletions

View File

@ -1,3 +1,8 @@
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>

View File

@ -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