Re: Error message doesn't say, "error"

[Bruce Korb]

Hi Eric,

On Sat, Nov 14, 2009 at 10:04 AM, Eric Blake <address@hidden> wrote:
> According to Bruce Korb on 11/14/2009 11:01 AM:
>> that includes 140 lines of warning messages all caused by gnulib
>
> We've brought that up before, but Bruno didn't like Ralf's patch to
> silence the warnings in his macros.  For now, you'll just have to ignore
> warnings there.

OK, I'll bring it up again then:  THIS IS TOO HARD TO DEBUG WHEN THERE
IS THAT MUCH CHAFF IN THE OUTPUT!!!

If there is an emotional attachment to being able to see chaff, then
check for VERBOSE=true in the environment.  Forcing hapless coders
to wade through hundreds of lines of meaningless chatter to try
to find an error message that is not marked with "ERROR:" is simply
way, way, way too much of a burden on anybody that does not live
and breathe gnulib/autoconf stuff all day long.

Sorry, meaning no offense, Bruno, I just vehemently hate pointless chaff.

Thanks - Bruce