Sorry for the late reply. I totally missed your bug report. * Evgeni Golov <evg...@debian.org> [2014-03-23 14:38]: > Those errors might look like this in the build log: > > checking for idna_to_ascii_from_locale... no > ../configure: line 12285: test: =: unary operator expected > > This usually means that there is a syntax error in the configure script > but the execution could be completed. Syntax errors can lead to > unexpected configuration results.
Do you have an example of a buildd log that contains a line like that? I did a manual scan of all packages currently in unstable with the regexp you gave and could not find any example. > Those errors might look like this in the build log: > > checking for idna_to_ascii_from_locale... no > ../configure: line 12285: test: =: unary operator expected > > This usually means that there is a syntax error in the configure script > but the execution could be completed. Syntax errors can lead to > unexpected configuration results. > --- > data/bls/descriptions/X-configure-syntax-error.description | 14 > ++++++++++++++ > 1 file changed, 14 insertions(+) > create mode 100644 data/bls/descriptions/X-configure-syntax-error.description > > diff --git a/data/bls/descriptions/X-configure-syntax-error.description > b/data/bls/descriptions/X-configure-syntax-error.description > new file mode 100644 > index 0000000..7df52f6 > --- /dev/null > +++ b/data/bls/descriptions/X-configure-syntax-error.description > @@ -0,0 +1,14 @@ > +## Match: regexp:.*configure: line [0-9]\+: I'd would have expected that regexp to be quite expensive due to the starting with .* but it currently hardly increases the number of states in the compile finite state machine and it really cannot be helped that much I guess it does not matter. > +This is an experimental tag. It needs review and a better description. > +<br> > +The build log contains a message from <tt>configure</tt> starting with > +<pre> > +configure: line X: > +</pre> > +<br> > +This message usually means that there is a syntax error in the configure > +script, but the execution could be completed. Syntax errors can lead to > +unexpected configuration results. > +<br> > +If you have more information for this description or want it escalated > +to warning or error, please let me know. I guess it makes sense to start with an warning right away (I guess error is a bit too hard as it might not be an actual problem) I guess a longer description might be nice but currently the only thing I can think of is perhaps making the example line a bit more specific like > +configure: line NNN: SOME-ERROR-MESSAGE Bernhard R. Link -- F8AC 04D5 0B9B 064B 3383 C3DA AFFC 96D1 151D FFDC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org