aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGlenn Morris2014-12-15 19:30:50 -0800
committerGlenn Morris2014-12-15 19:30:50 -0800
commit15426191a1353ac208d8ebe4a5920228e0df41a4 (patch)
tree0f49d3334170daf4519b6fa001b6c07f8f88ee9d
parent1fc1f89341daa10f9318f60d03493b5bbfd7e12e (diff)
downloademacs-15426191a1353ac208d8ebe4a5920228e0df41a4.tar.gz
emacs-15426191a1353ac208d8ebe4a5920228e0df41a4.zip
* test/automated/data/flymake/Makefile: Comment.
-rw-r--r--test/automated/data/flymake/Makefile6
1 files changed, 4 insertions, 2 deletions
diff --git a/test/automated/data/flymake/Makefile b/test/automated/data/flymake/Makefile
index a92db78b46f..0f3f39791c8 100644
--- a/test/automated/data/flymake/Makefile
+++ b/test/automated/data/flymake/Makefile
@@ -2,9 +2,11 @@
2 2
3CC_OPTS = -Wall 3CC_OPTS = -Wall
4 4
5## Recent gcc's (e.g. 4.8.2 on RHEL7) can automatically colorize their output, 5## Recent gcc (e.g. 4.8.2 on RHEL7) can automatically colorize their output,
6## which can confuse flymake. Set GCC_COLORS to disable that. 6## which can confuse flymake. Set GCC_COLORS to disable that.
7## TODO is this something that should be fixed in flymake? 7## This only seems to be an issue in batch mode, where you would not
8## normally use flymake, so it seems like just avoiding the issue
9## in this test is fine. Set flymake-log-level to 3 to investigate.
8check-syntax: 10check-syntax:
9 GCC_COLORS= $(CC) $(CC_OPTS) ${CHK_SOURCES} 11 GCC_COLORS= $(CC) $(CC_OPTS) ${CHK_SOURCES}
10 12