maybe mention in the developer README how to bring back verbose build output.
--
---> Dirk Jagdmann
> http://cubic.org/~doj
-> http://llg.cubic.org
___
Sent via:Wireshark-dev mailing list
Archives:http://www.
On Feb 4, 2013, at 7:59 PM, Guy Harris wrote:
>
> On Feb 1, 2013, at 1:35 PM, Gerald Combs wrote:
>
>> Would anyone object to enabling silent build rules by default in
>> configure.ac (line 691)? It drastically reduces the amount of output
>> during compilation.
>
> ...if the Makefile.am files
On Feb 1, 2013, at 1:35 PM, Gerald Combs wrote:
> Would anyone object to enabling silent build rules by default in
> configure.ac (line 691)? It drastically reduces the amount of output
> during compilation.
...if the Makefile.am files were processed by a sufficiently recent version of
automak
On 2/2/13 5:10 AM, Jaap Keuter wrote:
> On 02/01/2013 10:35 PM, Gerald Combs wrote:
>> Would anyone object to enabling silent build rules by default in
>> configure.ac (line 691)? It drastically reduces the amount of output
>> during compilation. For example
>>
>> CC file.lo
>>
>> replaces
On Feb 2, 2013, at 5:10 AM, Jaap Keuter wrote:
> On 02/01/2013 10:35 PM, Gerald Combs wrote:
>> Would anyone object to enabling silent build rules by default in
>> configure.ac (line 691)? It drastically reduces the amount of output
>> during compilation. For example
>>
>> CC file.lo
>>
On 02/01/2013 10:35 PM, Gerald Combs wrote:
> Would anyone object to enabling silent build rules by default in
> configure.ac (line 691)? It drastically reduces the amount of output
> during compilation. For example
>
> CC file.lo
>
> replaces a screen full of text. You would still be abl
Would anyone object to enabling silent build rules by default in
configure.ac (line 691)? It drastically reduces the amount of output
during compilation. For example
CC file.lo
replaces a screen full of text. You would still be able to show verbose
output with "configure --disable-silent-
