Re: _AC_PROG_CXX_EXIT_DECLARATION: don't `#include '

2005-11-23 Thread David Thompson
Looking into this further. Here is the problem I'm seeing. (Autoconf 2.5.9 on cygwin). The function is defined as: m4_define([_AC_PROG_CXX_EXIT_DECLARATION], [for ac_declaration in \ '' \ 'extern "C" void std::exit (int) throw (); using std::exit;' \ 'extern "C" void std::exit (int); u

2.53 doesn't work on MacOS X

2002-03-26 Thread David Thompson
I just wanted somebody to know that I've been trying to test 2.53 on MacOS X and it just plain doesn't work. I'm not sure where it is breaking, but after running autoconf on my configure.in, the configure file begins as follows: #! /bin/sh # Guess values for system-dependent variables and crea

AC_CHECK_HEADERS long list error

2002-03-27 Thread David Thompson
If I have a large number of headers to check for with AC_CHECK_HEADERS--say 20 items, I don't want to have to put them all on the same line. So I do something like the following: AC_CHECK_HEADERS( file.h file1.h ... file6.h \ file7.h file8.h ... file12.h \ file13.h) However, the code produced

Re: AC_CHECK_HEADERS long list error

2002-03-27 Thread David Thompson
> AC_CHECK_HEADERS( file.h file1.h ... file6.h \ > file7.h file8.h ... file12.h \ > file13.h) > > However, the code produced by the macro doesn't copy the '\' so it > sees the newline and obviously breaks. Is there anyway around this > other than to write a bunch of AC_CHECK_HEADERS (thus e

Re: AC_CHECK_HEADERS long list error

2002-03-27 Thread David Thompson
I did try this and it still didn't help. As for the '\' in quoting; didn't try that--but now that this has been brought up--somebody in the know can look at it as a bug and I'll just use multiple AC_CHECK_HEADERS lines. At 6:11 PM -0500 3/27/02, Harlan Stenn wrote: >Off the top of my head and

Re: AC_CHECK_HEADERS long list error

2002-03-27 Thread David Thompson
This is with autoconf 2.52. David Lars Hecking writes: > > > AC_CHECK_HEADERS( file.h file1.h ... file6.h \ > > file7.h file8.h ... file12.h \ > > file13.h) > > > > However, the code produced by the macro doesn't copy the '\' so it > > sees the newline and obviously breaks. Is there anywa

Re: 2.53 doesn't work on MacOS X

2002-04-03 Thread David Thompson
AILED near `acfunctions.at:21' 150: acfunctions.at:22 FAILED near `acfunctions.at:22' 151: acfunctions.at:23 FAILED near `acfunctions.at:23' 152: acfunctions.at:24 FAILED near `acfunctions.at:24' 153: acfunctions.at:25 FAILED near `acfunctions.at:25' 154: acfunctions.at:26 FAIL

Re: Autoconf 2.54 is released

2002-09-17 Thread David Thompson
Akim, et. al., I've tried upgrading to 2.53 and 2.54 and both produce a configure that is unusable for our product. 2.52 produces a good configure. At the top of the configure I get something that looks like ECHO_T= ECHO_N... I've seen one other person have this problem on a user group but no

_AC_PROG_CXX_EXIT_DECLARATION problem

2004-04-20 Thread David Thompson
Since this function has been modified at version 1.179, it now breaks our configure process on Windows with Microsoft compilers. The problem is, that the appropriate configuration is just #include with no prototype. This option for the test was removed so it never completes correctly. The test

Re: _AC_PROG_CXX_EXIT_DECLARATION problem

2004-04-20 Thread David Thompson
? I looked in the autoconf.m4f file and it appears to be the same code that is in c.m4 for the function. Any pointers? David At 3:20 PM -0700 4/20/04, Paul Eggert wrote: David Thompson <[EMAIL PROTECTED]> writes: Since this function has been modified at version 1.179, it now break