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 because it looks like Linux and Linux is cool. This is exactly the problem that I was concerned about and why I fought to ensure that it is not enabled by default. Unfortunately, it was made very easy for a package author to enable by default and some package authors are now doing so even though it makes open source software seem confusing and inconsistent.

It means automake is pushing around package maintainers to modify their packages to automake's behavioral changes.

Quite annoying indeed.

Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


_______________________________________________
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf

Reply via email to