Re: I've been requested to report a bug by configure :-)

[Akim Demaille]

| configure: WARNING: X11/extensions/Xvlib.h: present but cannot be compiled
| configure: WARNING: X11/extensions/Xvlib.h: check for missing prerequisite 
| headers?
| configure: WARNING: X11/extensions/Xvlib.h: proceeding with the 
preprocessor's 
| result
| configure: WARNING:     ## ------------------------------------ ##
| configure: WARNING:     ## Report this to address@hidden ##
| configure: WARNING:     ## ------------------------------------ ##
| 
| I guess this report needs more information to be usefull but I don't know 
what 
| you need. So if someone tells me what's required I can try to provide more 
| usefull information. 
| 
| autoconf: 2.57
| gcc: 3.2.2
| 
| Bye David
| 



Please, report this to the package maintainers, as it's a configure.ac
problem.  The Autoconf 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
   ])