autoconf
[Top][All Lists]
Advanced

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

warnings from AC_CHECK_HEADERS because header is present but cannot be c


From: Ed Hartnett
Subject: warnings from AC_CHECK_HEADERS because header is present but cannot be compiled...
Date: Sat, 04 Jun 2005 10:43:31 -0600
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.4 (gnu/linux)

Howdy all!

When I run the configure for HDF5, an open-source scientific data
library, I get the following warning:

checking winsock.h presence... yes
configure: WARNING: winsock.h: present but cannot be compiled
configure: WARNING: winsock.h:     check for missing prerequisite
headers?
configure: WARNING: winsock.h: see the Autoconf documentation
configure: WARNING: winsock.h:     section "Present But Cannot Be
Compiled"
configure: WARNING: winsock.h: proceeding with the preprocessor's
result
configure: WARNING: winsock.h: in the future, the compiler will take
precedence
configure: WARNING:     ## ------------------------------------ ##
configure: WARNING:     ## Report this to address@hidden ##
configure: WARNING:     ## ------------------------------------ ##
checking for winsock.h... yes

1 - Is there any way to turn this warning off? I really don't want
users emailing this to the hdf support staff, since their answer is
going to be: just ignore it.

2 - Is there any way to make autoconf go with the "future" behavior
now, and say that winsock.h is not present, since it can't be
compiled?

The info pages rather imply that this test should fail, since
winsock.h is not compilable. What am I missing?

>From info:

   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::).

Thanks!

Ed




-- 
Ed Hartnett  -- address@hidden





reply via email to

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