configure output summary

[Josip Rodin]

On Wed, Nov 17, 2010 at 07:53:02AM +0100, Stefan Winter wrote:
> I think it would generally make sense to put a summary output of  
> configure at the end of its run, so that one can easily see which  
> modules will be disabled.
>
> In an acute case of bash script fiddling, I created the attached proof  
> of concept "test.sh" script, which recursively goes through all  
> config.log files and
>
> a) greps all lines with WARNING
> b) greps all lines with "silently not building"
>
> and puts these out in massaged human-readable form. Would something like  
> this have any chances of getting included into the tarball? It could run  
> as the very last thing in configure...

I've actually been a bit confused by the notion of having separate autoconf
installations/invocation in multiple subdirectories. The point of that would
seem to be that if you just want to reconfigure and rebuild one particular
part, you can do it.

But who ever does that?

It seems to me that everyone only ever wants a single autoconf instance for
the whole tree, which can generate all the subdirectory makefiles.

-- 
     2. That which causes joy or happiness.