Re: BUG

[Akim Demaille]

| Hallo,
| during configure the gimp-1.2.3 a bug comes out.
| The short text-file is attatched.
| 
| Best Regards
| 
| U. Engelmann
| 
| checking for GTK - version >= 1.2.8... yes
| checking math.h usability... yes
| checking math.h presence... yes
| checking for math.h... yes
| checking ieeefp.h usability... yes
| checking ieeefp.h presence... yes
| checking for ieeefp.h... yes
| checking for extra flags to get ANSI library prototypes... none needed
| checking for extra flags for POSIX compliance... none needed
| checking for XmuClientWindow in -lXmu... yes
| checking X11/Xmu/WinUtil.h usability... no
| checking X11/Xmu/WinUtil.h presence... yes
| configure: WARNING: X11/Xmu/WinUtil.h: present but cannot be compiled
| configure: WARNING: X11/Xmu/WinUtil.h: check for missing prerequisite headers?
| configure: WARNING: X11/Xmu/WinUtil.h: proceeding with the preprocessor's 
resultconfigure: WARNING:     ## ------------------------------------ ##
| configure: WARNING:     ## Report this to address@hidden ##
| configure: WARNING:     ## ------------------------------------ ##
| checking for X11/Xmu/WinUtil.h... yes
| checking for aa_printf in -laa... yes
| checking aalib.h usability... yes
| checking aalib.h presence... yes
| checking for aalib.h... yes
| checking for TIFFReadScanline in -ltiff... yes
| checking tiffio.h usability... yes
| checking tiffio.h presence... yes
| checking for tiffio.h... yes

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
   ])