[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
_AC_PROG_CXX_EXIT_DECLARATION oddity
From: |
Daniel Elstner |
Subject: |
_AC_PROG_CXX_EXIT_DECLARATION oddity |
Date: |
Sat, 21 Jul 2001 06:08:43 +0200 |
Hello,
Why does _AC_PROG_CXX_EXIT_DECLARATION try '#include <stdlib.h>' first,
before the trying the prototypes?
Here's the ChangeLog entry:
2001-01-22 Lars J. Aas <address@hidden>
* aclang.m4 (_AC_PROG_CXX_EXIT_DECLARATION): First try no declaration,
then '#include <stdlib.h>', before trying the explicit declarations.
Is there any chance left that the explicit declaration will be used?
I ask that because it breaks my configure script. There's e.g. a check
for select(), which has its prototype included by <stdlib.h> on my
system. Of course this fails when checking for select with the C++
compiler.
You may say I should use the C compiler for this test, but since I use
this function in C++ code I should check it with the C++ compiler, too.
IMHO.
Anyway, what's the sense of that behaviour?
Any advice would be greatly appreciated,
--Daniel
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- _AC_PROG_CXX_EXIT_DECLARATION oddity,
Daniel Elstner <=