Identify autoconf, gcc and clang errors and warnings

[unix-junkie]

Currently, the build runner can tell which particular phase (the configure, the build or the test) has failed and raise a separate build problem.

It would make sense, however, to implement a smarter behaviour and detect the standard autoconf, gcc and clang error messages and warnings, most probably using the Process Output Parsers plug-in.