The current "GNU Make and GNU C Compiler" parser for the warnings plugin does not seem trap many make errors. For example I had a build which generated the following error:

gmake: *** No rule to make target 'myfile.cpp', needed by 'otherfile.obj'.

This error was not picked up by the compiler parser (actually the TI CCS one) or by the GNU Make part of the above parser. This made it very difficult to spot the error in the very large console log.

Looking at the warnings plugin code for GnuMakeGccParser.java it only seems to define a regex rule to match make entering a directory, it seems to contain no other regex rules to trap make errors. Maybe I am misunderstanding the parser capability but I was expecting it to pick up some/all of the standard make errors as documented here.

I was able to add a one-off warnings parser trap for the "no rule" error under the Jenkins Compiler Warnings configuration, however I don't think it would be possible to craft a regex which would cover all make error messages and therefore adding multiple extra parsers there is probably not the best solution and it really should go in the parser itself.

Would it be possible to extend the GNU Make parser to trap all possible make errors. I noted that a similar exercise was done for the CDT module within Eclipse, as detailed in this bug post, with java code attached to comment #1. This may be a useful starting point.