[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] build: use automake's --silent-rules option when possible

From: Russ Allbery
Subject: Re: [PATCH] build: use automake's --silent-rules option when possible
Date: Sat, 28 Mar 2009 21:49:31 -0700
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)

Ralf Corsepius <address@hidden> writes:
> Jim Meyering wrote:

>> Since I bootstrap using automake from its "next" branch, it's
>> enabled for me.  And that translates to enhanced
>> files in the tarballs I generate.  The net result is that when
>> you run "make" (using distributed files), you'll
>> see something like this:

>>  ...
>>  CC  id.o

> Now your users won't see the "silent bugs" your package comes with.

I'm planning on doing the same thing with my packages because I think my
users will see the bugs *better*.  One of the problems with the default
Automake output is that it's very difficult, without redirecting output or
the assistance of a separate parsing program, to extract the warnings from
the long compiler strings.  This format makes the warnings *far* more
obvious, which is very useful.

The only thing that I'm worried about is not seeing the list of libraries
with which executables are linked.  That's the single piece of debugging
information about builds that I use the most often.

But the long, repetitive compiler lines, which are mechanically generated
and rarely contain useful information, get in the way of seeing bits of
output that are actually important.

Russ Allbery (address@hidden)             <>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]