Commit | Line | Data |
---|---|---|
b11fb939 KR |
1 | /* conf.in. Generated automatically from configure.in by autoheader. */ |
2 | ||
3 | /* Define if using alloca.c. */ | |
4 | #undef C_ALLOCA | |
5 | ||
6 | /* Define to one of _getb67, GETB67, getb67 for Cray-2 and Cray-YMP systems. | |
7 | This function is required for alloca.c support on those systems. */ | |
8 | #undef CRAY_STACKSEG_END | |
9 | ||
10 | /* Define if you have <alloca.h> and it should be used (not on Ultrix). */ | |
11 | #undef HAVE_ALLOCA_H | |
12 | ||
13 | /* Define as __inline if that's what the C compiler calls it. */ | |
14 | #undef inline | |
15 | ||
16 | /* If using the C implementation of alloca, define if you know the | |
17 | direction of stack growth for your system; otherwise it will be | |
18 | automatically deduced at run-time. | |
19 | STACK_DIRECTION > 0 => grows toward higher addresses | |
20 | STACK_DIRECTION < 0 => grows toward lower addresses | |
21 | STACK_DIRECTION = 0 => direction of growth unknown | |
22 | */ | |
23 | #undef STACK_DIRECTION | |
24 | ||
b11fb939 KR |
25 | /* Should gas use high-level BFD interfaces? */ |
26 | #undef BFD_ASSEMBLER | |
27 | ||
28 | /* Some assert/preprocessor combinations are incapable of handling | |
29 | certain kinds of constructs in the argument of assert. For example, | |
30 | quoted strings (if requoting isn't done right) or newlines. */ | |
31 | #undef BROKEN_ASSERT | |
32 | ||
33 | /* If we aren't doing cross-assembling, some operations can be optimized, | |
34 | since byte orders and value sizes don't need to be adjusted. */ | |
35 | #undef CROSS_COMPILE | |
36 | ||
37 | /* Some IBM compilers can't handle some of the (rather basic) constructs | |
38 | used in the 68k support code. */ | |
39 | #undef IBM_COMPILER_SUX | |
40 | ||
41 | /* Some gas code wants to know these parameters. */ | |
42 | #undef TARGET_ALIAS | |
43 | #undef TARGET_CPU | |
44 | #undef TARGET_CANONICAL | |
45 | #undef TARGET_OS | |
46 | #undef TARGET_VENDOR | |
47 | ||
48 | /* Some operating systems, for example DOS, require the use of "wb" mode when | |
49 | opening a binary file for writing. If only "w" is used, the file will not | |
50 | be correct. However, some other systems reject such a mode. This indicates | |
51 | which ../include/fopen-*.h header file we want to include, so that we can | |
52 | get macros that'll do the right thing for this system. */ | |
53 | #undef WANT_FOPEN_BIN | |
54 | ||
55 | /* Sometimes the system header files don't declare malloc and realloc. */ | |
bf111c9f | 56 | #undef NEED_DECLARATION_MALLOC |
b11fb939 KR |
57 | |
58 | /* Sometimes the system header files don't declare free. */ | |
bf111c9f | 59 | #undef NEED_DECLARATION_FREE |
b11fb939 KR |
60 | |
61 | /* Sometimes errno.h doesn't declare errno itself. */ | |
bf111c9f | 62 | #undef NEED_DECLARATION_ERRNO |
b11fb939 KR |
63 | |
64 | #undef MANY_SEGMENTS | |
65 | ||
66 | /* Needed only for sparc configuration */ | |
67 | #undef sparcv9 | |
68 | ||
69 | /* Define if you have the <errno.h> header file. */ | |
70 | #undef HAVE_ERRNO_H | |
71 | ||
72 | /* Define if you have the <memory.h> header file. */ | |
73 | #undef HAVE_MEMORY_H | |
74 | ||
75 | /* Define if you have the <stdarg.h> header file. */ | |
76 | #undef HAVE_STDARG_H | |
77 | ||
78 | /* Define if you have the <stdlib.h> header file. */ | |
79 | #undef HAVE_STDLIB_H | |
80 | ||
81 | /* Define if you have the <string.h> header file. */ | |
82 | #undef HAVE_STRING_H | |
83 | ||
84 | /* Define if you have the <strings.h> header file. */ | |
85 | #undef HAVE_STRINGS_H | |
86 | ||
87 | /* Define if you have the <sys/types.h> header file. */ | |
88 | #undef HAVE_SYS_TYPES_H | |
89 | ||
90 | /* Define if you have the <unistd.h> header file. */ | |
91 | #undef HAVE_UNISTD_H | |
92 | ||
93 | /* Define if you have the <varargs.h> header file. */ | |
94 | #undef HAVE_VARARGS_H |