On Sun, Nov 27, 2005 at 10:08:44PM -0800, Paul Eggert wrote: > Albert Chin <[EMAIL PROTECTED]> writes: > > > We've currently solved it by implementing > > separate defines depending on the language. > > That doesn't sound quite right. If you compile with different C > compilers, or the same C compiler with differing options, you should > have to rerun 'configure'. The same sort of thing should occur if > you compile with both a C and a C++ compiler; in effect you need > run 'configure' more than once. > > It might be possible to generalize Autoconf to support multiple (and > incompatible) compilers used for the same project, but that'd be a > bigger undertaking.
Huh? I'm talking about _one_ project with two languages, C and C++. In such a project, if human.h includes <stdint.h> because of HAVE_STDINT_H, how should a C++ source file #include "human.h" correctly when <stdint.h> isn't available to the C++ compiler? -- albert chin ([EMAIL PROTECTED]) _______________________________________________ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib
