On Sun, Nov 27, 2005 at 10:08:44PM -0800, Paul Eggert wrote: > 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.
That's not so convenient if you want to mix C code and C++ code in the same binary. > 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. Some parts of GNU CSSC are compiled with C, but most is C++. The configure script is just run once, and everything works fine. However, only a tiny fraction of CSSC is actually pure C (just Allman's sccs.c and a couple of test utilities in fact), and C and C++ are not mixed in the same binary, so this just works in the case of CSSC. However I'm quite happy to believe that this is working by accident rather than by design. FWIW, CSSC doesn't use gnulib, though. James. _______________________________________________ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib
