On Mon, Jun 13, 2005 at 02:21:56PM -0500, Tom Duerbusch wrote: > Yep, I do have the 'config.log'...thanks > > I took one look at it and saw the #define stuff and decided that was > not a log file but I thought it may have been a temp file for some "c" > code.
Tom, That's part of how configure scripts work. Some capabilities can be tested by checking to see if a file is present or the like. Other capabilities can only be tested by compiling a bit of code and seeing what happens when you run it (or seeing what error you get from the compiler when you compile it). The code you see in the config.log is the small code snippets that are compiled and (usually) run as part of the configure process. So you weren't seeing things! :) The config.log file is very thorough, so just to pick up the message output you could redirect (or use "tee"), or use "script", as already suggested. Cheers, Vic Cross ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
