Re: subtle problem of font-lock in *compilation* buffer

[Chong Yidong]

Kenichi Handa <address@hidden> writes:

> In *compilation* buffer, font-lock thinks that this kind of
> line is an error message:
>
> /bin/sh ../libtool --tag=CC --mode=link gcc  -g -Wall --pedantic   -o 
> libm17n-core.la -rpath /usr/local/lib -export-dynamic -version-info 1:0:1 
> character.lo chartab.lo plist.lo m17n-core.lo mtext.lo symbol.lo textprop.lo 
> mtext-lbrk.lo mtext-wseg.lo -L/usr/lib -lxml2 -lz -lpthread -lm 
> -L/usr/local/lib -lthai   -ldl 
>
> That is perhaps because of "1:0:1".

How can the compilation font-lock pattern distinguish this from a
legitimate error message?  Maybe this is too hard to solve (and it
seems to be a fairly uncommon situation).