On 10/13/2009 04:49 PM, Bob Friesenhahn wrote:
On Tue, 13 Oct 2009, Ralf Corsepius wrote:
The problem is verifying "correctness of building" packages in batches.
i.e. to monitor/inspect CFLAGS, CPPFLAGS, LDFLAGS etc. in compiler
calls etc. for correctness
(NB: A package, which compiles without warning doesn't mean it is
being built correctly.)
What work does it cause except for using --disable-silent-rules at
configure time or V=1 at make time?
Exactly this is the problem.
The problem isn't the support for silent rules. The problem is that
some packages are enabling it by default
Indeed. What makes the situation worse is some upstreams shipping
"common" aclocal-macros which enable it by default. This cause quite
some amount of surprises when analysing buildlogs of packages which for
whatever reasons run autoreconf/autogen.sh.
because it looks like Linux and Linux is cool.
:=)
Ralf
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
