Re: _AC_PROG_CXX_EXIT_DECLARATION problem

[David Thompson]

I've narrowed this down further. It appears to be a problem with 
autoconf.m4f. If I move autoconf.m4f to autoconf-hold.m4f, regenerate 
my configure, configure works right. I'm not into internals of 
autom4te stuff--so is there something I should check? Why would this 
make a difference? 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 breaks
 our configure process on Windows with Microsoft compilers. The problem
 is, that the appropriate configuration is just #include <stdlib.h>
 with no prototype.
That's the first choice of _AC_PROG_CXX_EXIT_DECLARATION; it sets
ac_declaration to the empty string, and then tries to compile a program
like this:
  $ac_declaration
  @%:@include <stdlib.h>
which expands to

  #include <stdlib.h>

which is what you're asking for.

 For some reason, the case where stdlib and no prototype never runs (at
 least we never see it in the config.log.)
 Could this be a problem with bash or is there an error in the write of
 this function?
It could be either, but you need to investigate more what's going on.
You might try runing "configure" with "sh -x configure".


--
.............................................................................
David L. Thompson                   Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED]    5515 Skyway Drive, Missoula, MT 59804
                                    Phone : (406)756-7472