On Fri, Aug 18, 2006 at 01:24:06PM -0500, Steve Greenland wrote:
> No sign of what it actually did, no sign of whether the answer was
> yes or no. Yes, there is some stuff in there. But not always enough.
> Sometimes it spits out what the compile command was, and the code used,
> and sometimes it doesn't.
If you want more information you can always do "bash -xv ./configure
..."
> Hmmm, why is it checking for "string.h" and "limits.h" after it has
> already checked for "ANSI C header files"?
Because whoever created configure.ac told it to do so?
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
