Keith Bostic wrote:
> I'd like to make a small suggestion for autoconf -- it would be helpful
> in debugging configuration problems if the output that is displayed on
> the screen during configuration [...] were also copied into the
>config.log output.
That feature has already been incorporated into the CVS version of autoconf.
> I would also encourage putting the source for all test programs into the
> config.log file too, not just the failed ones. I don't know about other
> folks, but we use config.log for the sole purpose of debugging problems,
> and so the more information we can get in that file, the better off we are.
I don't see the connection. If a test program didn't cause an error, why
do you need to see it? Could you give an example? (And after all, the
source code of the test program is in the configure script if you really
need to see it.)
Cordially,
Steven G. Johnson
