When I try to build & test just libstdc++, or to run the testsuite from trunk against my installed libstdc++, the testsuite tries to pass "-fdiagnostics-color=never" to the system GCC, which is too old to know what that is. Since I really just want to test a patch for the gdb pretty-printers, and since evidently my machine is too puny to actually build GCC, this is a bit problematic. According to the documentation, setting GCC_COLORS to "" in the environment should be just as effective, while it clearly can't cause older GCCs to freak out, so that's just what I've done. (I've also taken the liberty of swapping the "set ccflags" and "set cxxflags" lines here so that ccflags doesn't end up with two "-DLOCALEDIR" flags.) libstdc++-v3/ * testsuite/lib/libstdc++.exp (libstdc++_init): Set $GCC_COLORS="" instead of insisting that GCC understand -fdiagnostics-color=never Signed-off-by: Samuel Bronson --- libstdc++-v3/testsuite/lib/libstdc++.exp | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)