/* Top of my file (acconfig.h is the ultimate source file) */ @TOP@ /* This file is like the acconfig.h file provided by Autoconf, * but explains those #defines that are local to this package. */ /* Location of the "diff" command. */ #undef CONFIG_DIFF_COMMAND /* HAVE_GNU_DIFF is defined if the CONFIG_DIFF_COMMAND is GNU diff. * This affects the commentary we produce in showconfig.cc. */ #undef HAVE_GNU_DIFF /* The package name and version are macros are created by automake but * not understood by autoheader. Hence I have to point out their * existence to autoheader by putting them here... */ /* Package name. */ #undef PACKAGE /* Package version. */ #undef VERSION /* Is it safe to rely on POSIX saved IDs? */ #undef SAVED_IDS_OK /* Do we disallow the creation of "binary" (encoded) SCCS files? */ /* This is controlled by the --enable-binary and --disable-binary */ /* options to configure. */ #undef CONFIG_DISABLE_BINARY_SUPPORT /* What is the maximum length of line which we will allow CSSC to put * into an SCCS file? Zero means that there is no limit. * This is controlled by the --enable-max-line-length option to * configure. */ #undef CONFIG_MAX_BODY_LINE_LENGTH @BOTTOM@ /* This section contains those comments and definitions that are too * complex for autoheader.m4 to understand; autoheader works by * redefining the autoconf primitives in such a way that it gains a * record of what might or might not get defined, just by m4 expansion * of congigure.in. It doesn't seem clever enough to cope with the * macros AC_CHECK_GLOBAL and AC_CHECK_DECL_IN_HEADER, because both of * those use AC_CACHE_VAL, which forces us to use a two-stage process * of getting the cached value or figuring it out, and then calling * AC_DEFINE etc. according to the result. It might be possible to * produce a local m4 file that provided appropriate definitions of * the macros in configure.in which helped acheader out in this, but I * can't see how to do it. Hence we work around this feature of * autoheader in this way. * -- James Youngman */ /* define if you have the ISO C function fsetpos(). */ #undef HAVE_FSETPOS /* ixemul.library on AmigaOS has a stub for fork(), but it does nothing. */ /* define if you have the Unix function fork() -- and it works. */ #undef HAVE_FORK /* define if you have the global variable timezone. */ #undef HAVE_TIMEZONE /* define if you have the global variable sys_nerr. */ #undef HAVE_SYS_NERR /* define if you have the global variable sys_errlist. */ #undef HAVE_SYS_ERRLIST /* define if declares sys_nerr. */ #undef ERRNO_H_DECLARES_SYS_NERR /* define if declares sys_nerr. */ #undef STDIO_H_DECLARES_SYS_NERR /* define if declares sys_errlist. */ #undef ERRNO_H_DECLARES_SYS_ERRLIST /* define if declares sys_errlist. */ #undef STDIO_H_DECLARES_SYS_ERRLIST /* define if declares sys_errlist. */ #undef STDLIB_H_DECLARES_SYS_ERRLIST /* define if either signal.h or unistd.h declares * sys_siglist[]. This is a BSD-ism, I think. * This corresponds to the AC_DECL_SIGLIST Autoconf macro. */ #undef SYS_SIGLIST_DECLARED /* Define if your C++ compiler can compile a program that uses * exceptions which will work when it is run. */ #undef HAVE_EXCEPTIONS /* Define HAVE_STD_NAMESPACE if your C++ compiler likes constructions like * "std::string s". A conforming C++ compiler should like that sort of stuff. * In fact, a conforming C++ compiler should insist on your saying * "using std;" before using a naked "string s" declaration. Anyway, if we * can say "std::string s", define this HAVE_STD_NAMESPACE. */ #undef HAVE_STD_NAMESPACE /* We also define the macro STD_NAMESPACE. This is used where one would * ordinarily put "std::" if one was talking to a proper C++ compiler. * However, we arrange for it to expand to nothing when we are talking * to a compiler which doesn't understand the "std::" in "std::string". */ #undef STD_NAMESPACE /* Bottom of my file (stop). */