>> 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?
Any time where the program succeeded, but it shouldn't have
i.e., I'm testing to see if a feature exists, and the script
concludes that it does -- but it actually doesn't.
As I said, I use config.log for debugging, that is, I only
look at it if something goes wrong. In which case, the more
information I have, the happier I am.
> (And after all, the
> source code of the test program is in the configure script if you really
> need to see it.)
I've had to do that a few times, and it's awfully hard to find
the actual code, even with the line numbers.
Regards,
--keith
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Keith Bostic
Sleepycat Software Inc. [EMAIL PROTECTED]
394 E. Riding Dr. +1-978-371-0408
Carlisle, MA 01741-1601 http://www.sleepycat.com
