old-cross-binutils/gas/conf.in
Ken Raeburn fb589130a8 * Makefile.in (prefix, exec_prefix): Use @-subtitutions.
* aclocal.m4 (AC_OUTPUT_LINKS): Deleted redefinition, since autoconf 1.109 has
this fixed.
* configure.in: Don't change quote characters around AC_MSG_ERROR invocation.
Don't use AC_HEADER_STDC, since it requires running a program.  Cache
NEED_*_DECLARATION values.
* configure, conf.in: Regenerated with a modified autoconf 1.109.
1994-08-31 21:50:38 +00:00

94 lines
3 KiB
Text

/* conf.in. Generated automatically from configure.in by autoheader. */
/* Define if using alloca.c. */
#undef C_ALLOCA
/* Define to one of _getb67, GETB67, getb67 for Cray-2 and Cray-YMP systems.
This function is required for alloca.c support on those systems. */
#undef CRAY_STACKSEG_END
/* Define if you have <alloca.h> and it should be used (not on Ultrix). */
#undef HAVE_ALLOCA_H
/* Define as __inline if that's what the C compiler calls it. */
#undef inline
/* If using the C implementation of alloca, define if you know the
direction of stack growth for your system; otherwise it will be
automatically deduced at run-time.
STACK_DIRECTION > 0 => grows toward higher addresses
STACK_DIRECTION < 0 => grows toward lower addresses
STACK_DIRECTION = 0 => direction of growth unknown
*/
#undef STACK_DIRECTION
/* Should gas use high-level BFD interfaces? */
#undef BFD_ASSEMBLER
/* Some assert/preprocessor combinations are incapable of handling
certain kinds of constructs in the argument of assert. For example,
quoted strings (if requoting isn't done right) or newlines. */
#undef BROKEN_ASSERT
/* If we aren't doing cross-assembling, some operations can be optimized,
since byte orders and value sizes don't need to be adjusted. */
#undef CROSS_COMPILE
/* Some IBM compilers can't handle some of the (rather basic) constructs
used in the 68k support code. */
#undef IBM_COMPILER_SUX
/* Some gas code wants to know these parameters. */
#undef TARGET_ALIAS
#undef TARGET_CPU
#undef TARGET_CANONICAL
#undef TARGET_OS
#undef TARGET_VENDOR
/* Some operating systems, for example DOS, require the use of "wb" mode when
opening a binary file for writing. If only "w" is used, the file will not
be correct. However, some other systems reject such a mode. This indicates
which ../include/fopen-*.h header file we want to include, so that we can
get macros that'll do the right thing for this system. */
#undef WANT_FOPEN_BIN
/* Sometimes the system header files don't declare malloc and realloc. */
#undef NEED_MALLOC_DECLARATION
/* Sometimes the system header files don't declare free. */
#undef NEED_FREE_DECLARATION
/* Sometimes errno.h doesn't declare errno itself. */
#undef NEED_ERRNO_DECLARATION
#undef MANY_SEGMENTS
/* Needed only for sparc configuration */
#undef sparcv9
/* Define if you have the <errno.h> header file. */
#undef HAVE_ERRNO_H
/* Define if you have the <memory.h> header file. */
#undef HAVE_MEMORY_H
/* Define if you have the <stdarg.h> header file. */
#undef HAVE_STDARG_H
/* Define if you have the <stdlib.h> header file. */
#undef HAVE_STDLIB_H
/* Define if you have the <string.h> header file. */
#undef HAVE_STRING_H
/* Define if you have the <strings.h> header file. */
#undef HAVE_STRINGS_H
/* Define if you have the <sys/types.h> header file. */
#undef HAVE_SYS_TYPES_H
/* Define if you have the <unistd.h> header file. */
#undef HAVE_UNISTD_H
/* Define if you have the <varargs.h> header file. */
#undef HAVE_VARARGS_H