X-Git-Url: https://code.delx.au/gnu-emacs/blobdiff_plain/b9345dfd4b5479ec624f1870723a8ea5c9c719e7..e48f6dd3f79229d1dca96a691069eba45e90480c:/etc/compilation.txt diff --git a/etc/compilation.txt b/etc/compilation.txt index 8e19222143..d26af20985 100644 --- a/etc/compilation.txt +++ b/etc/compilation.txt @@ -3,13 +3,13 @@ This shows the different kinds of messages compile recognizes by default and how they are rendered. It is intended both to help you decide which matchers you need and as a test of the matchers. Move the mouse over a colored part or -use `compilation-message-face', to see how much text was actually matched. +use 'compilation-message-face', to see how much text was actually matched. Note that the following example line should NOT be highlighted: Compilation started at Sat Jul 8 15:19:25 The important part is the symbol(s) line at the beginning of each entry. -These are the symbols you can customize `compilation-error-regexp-alist' for, +These are the symbols you can customize 'compilation-error-regexp-alist' for, to match the messages shown in that entry. A few complex cases have more than one symbol, which should be selected together. @@ -52,6 +52,7 @@ jikes are the ending line and ending column. [javac] /src/DataBaseTestCase.java:27: unreported exception ... [javac] /src/DataBaseTestCase.java:49: warning: finally clause cannot complete normally [jikes] foo.java:3:5:7:9: blah blah + [javadoc] c:\MyProject\Polynomial.java:560: error: unknown tag: math * Bash v2 @@ -254,12 +255,33 @@ foo.c:8.23-45: Informational: message foo.c:8-23: message foo.c:8-45.3: message foo.c:8.23-9.1: message +foo.el:3:1:Error: End of file during parsing jade:dbcommon.dsl:133:17:E: missing argument for function call G:/cygwin/dev/build-myproj.xml:54: Compiler Adapter 'javac' can't be found. file:G:/cygwin/dev/build-myproj.xml:54: Compiler Adapter 'javac' can't be found. {standard input}:27041: Warning: end of file not at end of a line; newline inserted +* Guile backtrace, 2.0.11 + +symbols: guile-file, guile-line + +Backtrace: +In ice-9/boot-9.scm: + 157: 6 [catch #t # ...] +In unknown file: + ?: 5 [apply-smob/1 #] +In ice-9/boot-9.scm: + 63: 4 [call-with-prompt prompt0 ...] +In ice-9/eval.scm: + 432: 3 [eval # #] +In unknown file: + ?: 2 [eval (main (command-line)) #] +In /home/janneke/vc/guile/examples/gud-break.scm: +1038: 1 [main ("gud-break.scm")] +1033: 0 [stderr "~a:hello world\n" (# # #)] + + * Lucid Compiler, lcc 3.x symbol: lcc @@ -307,6 +329,13 @@ made it more strict about the error message that follows. keyboard handler.c(537) : warning C4005: 'min' : macro redefinition d:\tmp\test.c(23) : error C2143: syntax error : missing ';' before 'if' d:\tmp\test.c(1145) : see declaration of 'nsRefPtr' +1>test_main.cpp(29): error C2144: syntax error : 'int' should be preceded by ';' +1>test_main.cpp(29): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int +1> +1>Build FAILED. +1> +1>Time Elapsed 00:00:01.46 +========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== * Open Watcom @@ -496,6 +525,16 @@ symbol: perl--Test # Failed test 1 in foo.t at line 6 +* Perl Test.pm module error messages comparing two values + +symbol: perl--Test2 + +# Test 3 got: "99" (d-compilation-perl.t at line 29) +# Expected: "88" (my test name) +# d-compilation-perl.t line 29 is: ok(99,88,'my test name'); + +# Test 6 got: "xx" (foo.t at line 33 fail #2) +# Expected: "yy" * Perl Test::Harness output @@ -513,13 +552,14 @@ index.html (13:1) Unknown element * Directory tracking -Directories are matched via `compilation-directory-matcher'. Files which are +Directories are matched via 'compilation-directory-matcher'. Files which are not shown as full paths are searched for relative to the directory where the message was issued. Entering directory `/a/b/c' Leaving directory `/a/b/c' -gmake[2]: Entering directory `/a/b/c' +make[2]: Entering directory '/a/b/c' +make[2]: Leaving directory '/a/b/c' makepp: Leaving directory `/a/b/c' @@ -535,9 +575,20 @@ checking whether to build shared libraries... yes checking whether -lc should be explicitly linked in... (cached) no checking For GLIB - version >= 2.0.0... yes (version 2.1.0) checking FONTCONFIG_CFLAGS... -g++ -o foo.o foo.cc -tool1 -output=foo foo.x -tool2 --outfile foo foo.y +tool -o foo.o foo.c +tool -o=foo.o foo.c +tool -output foo.o foo.c +tool -output=foo.o foo.c +tool -outfile foo.o foo.c +tool -outfile=foo.o foo.c +tool --output foo.o foo.c +tool --output=foo.o foo.c +tool --outfile foo.o foo.c +tool --outfile=foo.o foo.c +tool -omega foo.c foo2.c +tool -output-html-file foo.c foo2.c +tool --omega foo.c foo2.c +tool --output-html-file foo.c foo2.c Compilation started at Wed Jul 20 12:20:10 Compilation interrupt at Wed Jul 20 12:20:10 @@ -548,7 +599,7 @@ Compilation segmentation fault at Thu Jul 13 10:55:49 Compilation finished at Thu Jul 21 15:02:15 -Copyright (C) 2004-2011 Free Software Foundation, Inc. +Copyright (C) 2004-2016 Free Software Foundation, Inc. COPYING PERMISSIONS: