[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: coreutils 4.5.7 configure on Cray SV1ex
From: |
Akim Demaille |
Subject: |
Re: coreutils 4.5.7 configure on Cray SV1ex |
Date: |
Wed, 26 Feb 2003 11:19:35 +0100 |
User-agent: |
Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2 |
| checking sys/filsys.h usability... no
| checking sys/filsys.h presence... yes
| configure: WARNING: sys/filsys.h: present but cannot be compiled
| configure: WARNING: sys/filsys.h: check for missing prerequisite headers?
| configure: WARNING: sys/filsys.h: proceeding with the preprocessor's result
| configure: WARNING: ## ------------------------------------ ##
| configure: WARNING: ## Report this to address@hidden ##
| configure: WARNING: ## ------------------------------------ ##
| checking for sys/filsys.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
])