pgman wrote:
> > Also, the more such checks we provide in the hope of offering a "more
> > specific" error message, the greater the chance of providing a message
> > that is more specific and *wrong*, thus misleading the user and causing
> > him to waste time instead of save it.
> >
> > "Look in config.log" is good general-purpose advice for understanding
> > configure-detected problems. I don't think we should spend effort
> > on special-casing problems that are adequately explained if one looks
> > in the log.
>
> Where do we tell them to look in config.log? I have never see it.
OK, I found one mention of config.log in configure.in where it tries to
compile a test program. Are you saying you want more mentions of
config.log?
If I could add 50 lines to configure.in that would increase the number
of corrective error messages by 50%, I would do it right now.
---------------------------------------------------------------------------
AC_MSG_CHECKING([test program])
AC_TRY_RUN([int main() { return 0; }],
[ AC_MSG_RESULT(ok)],
[ AC_MSG_RESULT(failed)
AC_MSG_ERROR([[
*** Could not execute a simple test program. This may be a problem
*** related to locating shared libraries. Check the file 'config.log'
*** for the exact reason.]])],
[ AC_MSG_RESULT([cross-compiling])])
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
