Re: curlssl autoconf bug...

[Akim Demaille]

| I obtained curl-7.10.3 and did a "./configure" on a Solaris 8 machine with
| gcc 3.2.1 using the /usr/ccs/bin/ld loader.  I got the following error
| message that says I should report it to you:
| 
| 
| checking net/if.h usability... no
| checking net/if.h presence... yes
| configure: WARNING: net/if.h: present but cannot be compiled
| configure: WARNING: net/if.h: check for missing prerequisite headers?
| configure: WARNING: net/if.h: proceeding with the preprocessor's result
| configure: WARNING:     ## ------------------------------------ ##
| configure: WARNING:     ## Report this to address@hidden ##
| configure: WARNING:     ## ------------------------------------ ##
| checking for net/if.h... yes
| checking netinet/in.h usability... yes
| checking netinet/in.h presence... yes
| checking for netinet/in.h... yes
| checking netinet/if_ether.h usability... no
| checking netinet/if_ether.h presence... yes
| configure: WARNING: netinet/if_ether.h: present but cannot be compiled
| configure: WARNING: netinet/if_ether.h: check for missing prerequisite 
headers?
| configure: WARNING: netinet/if_ether.h: proceeding with the preprocessor's 
result
| configure: WARNING:     ## ------------------------------------ ##
| configure: WARNING:     ## Report this to address@hidden ##
| configure: WARNING:     ## ------------------------------------ ##
| checking for netinet/if_ether.h... yes
| 
| 
| There were other autoconf messages, but these were to be reported back to
| you.  So, I've done it.
| 
| Is there any other information that I should give you to help you figure out
| what went wrong?  

please, report this to the curl maintainers: it is their configure.ac
which has problems.  join the text below.  Thanks!

----------------------------------------

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