From: Akim Demaille <[EMAIL PROTECTED]>
   Date: 24 Jul 2000 10:56:01 +0200

   What would be the problem with enabling the use of the fourth
   parameter of AC_CHECK_FUNCS?  AC_CHECK_FUNC(func, yes, no, includes)?

That sounds right to me.  I didn't quite follow your patch, but I
assume the basic idea is to try to compile this program:

INCLUDES
int main () { return !FUNC; }

   I'm not sure we can enable the default includes right now though.

I would also be cautious here.  There are too many existing
configure.in files that assume you don't have to include anything to
check for a function's existence.

Perhaps if INCLUDES is `-' (or some other such symbol -- is there a
convention here?), then AC_CHECK_FUNCS could use the default includes.
An empty INCLUDES would mean to use the old AC_CHECK_FUNCS semantics
for now, but issue a deprecation warning since the plan is to switch
to using the default includes eventually.

Reply via email to