Daniel Stenberg wrote:

> The configure script now checks for header files differently than before, it
> no longer only checks for their presence, but also that they are "working".
>
> This has the side-effect that header files that can't be compiled stand-alone
> fail this test, unless we fix the configure.in file to properly include the
> prerequisite header files first. I need help to figure out what header files
> the failing headers require!
[...]
> Anyone?

I would suggest that you revert to an earlier version of autoconf,
until the autoconf maintainers provide some backwardscompatible
fix for their "new feature." This "feature" is obviously so
problematic for many projects using autoconf, that they cannot
ignore it.

Two alternatives:

 1. For the Triacle project I started building an autoconf
    lookalike in Perl (at the time autoconf only ran on Unix
    platforms, and the project required Perl anyways.) A minimal
    version that finds the compiler and compiler options, and
    which provides functionality such as finding headers,
    compiling code, and running code will get you a long way.

 2. Drop autoconf entirely. Instead use something like predef
    -- this has worked just fine for trio.

-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
Received on 2003-03-07