Might I ask the prerequisite question: why did we upgrade to 2.57 (I presume from 2.54?), and what did it gain us?

Is it an option to downgrade to 2.54, and just wait on the autoconf team to get enough people angry at them they might change it? I've had to sit on numerous packages due to upgrades which were rather undesireable....

My $0.02US is that they should have provided a way to disable actual compile tests (AC_CHECK_ONLY or something), leaving the old header-only behaviour. It seems a little onerous for them to put that burden of knowing what includes what...

(As it is now, I already move configure.in out of the way for RPMS because the previous autoconf/autobuild reconfigure doesn't work on all RedHat's, including my build machine)

-te

On Fri, Mar 07, 2003 at 02:16:18PM +0100, Daniel Stenberg wrote:
> Hi
>
> (This mail is cross-posted for attention, please keep follow-ups on the
> libcurl list.)
>
> We have problems with the configure script on several platforms, I need help.
>
> Before the 7.10.3 release, I upgraded to the latest autoconf (2.57) on the
> machine I build the release archives on. As you shall see below, the new
> additions from the fellows of the autoconf project have given us problems. To
> make things worse, the configure output says to report the issue to
> bug-autoconf_at_gnu.org, but they don't consider this a bug (as several people
> already mailed them about this).
>
> 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!
>
> Also, if more people with more platforms would join the "autobuild" system
> I've setup at http://curl.haxx.se/auto/, we would detect and fix problems
> already when they appear and we could even fix problems and have them tried
> out on systems we don't have physical access to...
>
> CURRENT PROBLEMS
>
> * Rohit Srivastava on HP-UX 11.00, configure doesn't detect a working
> select() for him and thus the script bails out...
>
> * Ray DeGennaro on AIX, configure complains that net/if.h doesn't work. I
> don't quite know what effect this causes, but it might cause compiler
> errors when building libcurl or so.
>
> * peter at kassies.com (bug report #694936, the email address bounces) filed
> problems on Solaris 8 with netinet/if_ether.h
>
> * Jeremie Petit (bug report #699293) experiences problems on Tru64 5.1 and
> the header file netinet/if_ether.h.
>
> So, I'm postponing the upcoming release in order to sort out some, if not
> all, of these issues first.
>
> Anyone?
>
> --
> Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
>
>
> -------------------------------------------------------
> 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

-- 
Troy Engel
GPG KeyID: DF3D5207
-------------------------------------------------------
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