bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: autoconf bug in kvirc3


From: Akim Demaille
Subject: Re: autoconf bug in kvirc3
Date: Wed, 26 Feb 2003 11:23:32 +0100
User-agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2


Please, report this to the package maintainers, as it's a configure.ac
problem.  The Autoconf 2.57 doc says:

      Previous versions of Autoconf merely checked whether the header was
   accepted by the preprocessor.  This was changed because the old test was
   inappropriate for typical uses.  Headers are typically used to compile,
   not merely to preprocess, and the old behavior sometimes accepted
   headers that clashed at compile-time.  If you need to check whether a
   header is preprocessable, you can use `AC_PREPROC_IFELSE' (*note
   Running the Preprocessor::).
   
      This scheme, which improves the robustness of the test, also requires
   that you make sure that headers that must be included before the
   HEADER-FILE be part of the INCLUDES, (*note Default Includes::).  If
   looking for `bar.h', which requires that `foo.h' be included before if
   it exists, we suggest the following scheme:
   
   
   AC_CHECK_HEADERS([foo.h])
   AC_CHECK_HEADERS([bar.h], [], [],
   [#if HAVE_FOO_H
   # include <foo.h>
   # endif
   ])

Thanks!

| Hi,
| when trying to compile de cvs version of kvirc3 (http://www.kvirc.net),
| if I execute the ./configure command, I receive this message:
| 
| checking dlfcn.h usability... yes
| checking dlfcn.h presence... no
| configure: WARNING: dlfcn.h: accepted by the compiler, rejected by the
| preprocessor!
| configure: WARNING: dlfcn.h: proceeding with the preprocessor's result
| configure: WARNING:     ## ------------------------------------ ##
| configure: WARNING:     ## Report this to address@hidden ##
| configure: WARNING:     ## ------------------------------------ ##
| checking for dlfcn.h... no
| 
| 
| If you need me to give more information, ask it to me.
| 
| Sergio.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]