📄 config.h.sh
字号:
case $CONFIG in'') if test ! -f config.sh; then ln ../config.sh . || \ ln ../../config.sh . || \ ln ../../../config.sh . || \ (echo "Can't find config.sh."; exit 1) echo "Using config.sh from above..." fi . ./config.sh ;;esacecho "Extracting config.h (with variable substitutions)"cat <<!GROK!THIS! >config.h/* config.h * This file was produced by running the config.h.SH script, which * gets its values from config.sh, which is generally produced by * running Configure. * * Feel free to modify any of this as the need arises. Note, however, * that running config.h.SH again will wipe out any changes you've made. * For a more permanent change edit config.sh and rerun config.h.SH. *//* EUNICE: * This symbol, if defined, indicates that the program is being compiled * under the EUNICE package under VMS. The program will need to handle * things like files that don't go away the first time you unlink them, * due to version numbering. It will also need to compensate for lack * of a respectable link() command. *//* VMS: * This symbol, if defined, indicates that the program is running under * VMS. It is currently only set in conjunction with the EUNICE symbol. */#$d_eunice EUNICE /**/#$d_eunice VMS /**//* CPPSTDIN: * This symbol contains the first part of the string which will invoke * the C preprocessor on the standard input and produce to standard * output. Typical value of "cc -E" or "/lib/cpp". *//* CPPMINUS: * This symbol contains the second part of the string which will invoke * the C preprocessor on the standard input and produce to standard * output. This symbol will have the value "-" if CPPSTDIN needs a minus * to specify standard input, otherwise the value is "". */#define CPPSTDIN "$cppstdin"#define CPPMINUS "$cppminus"/* CHARSPRINTF: * This symbol is defined if this system declares "char *sprintf()" in * stdio.h. The trend seems to be to declare it as "int sprintf()". It * is up to the package author to declare sprintf correctly based on the * symbol. *//* #$d_charsprf CHARSPRINTF /**//* FLEXFILENAMES: * This symbol, if defined, indicates that the system supports filenames * longer than 14 characters. */#$d_flexfnam FLEXFILENAMES /**//* index: * This preprocessor symbol is defined, along with rindex, if the system * uses the strchr and strrchr routines instead. *//* rindex: * This preprocessor symbol is defined, along with index, if the system * uses the strchr and strrchr routines instead. */#$d_index index strchr /* cultural */#$d_index rindex strrchr /* differences? *//* VOIDSIG: * This symbol is defined if this system declares "void (*signal())()" in * signal.h. The old way was to declare it as "int (*signal())()". It * is up to the package author to declare things correctly based on the * symbol. */#$d_voidsig VOIDSIG /**//* DIRHEADER: * This definition indicates which directory library header to use. */$d_dirheader/* HAVE_UNISTD_H: * This is defined if the system has unistd.h. */#$d_unistd HAVE_UNISTD_H /**//* Reg1: * This symbol, along with Reg2, Reg3, etc. is either the word "register" * or null, depending on whether the C compiler pays attention to this * many register declarations. The intent is that you don't have to * order your register declarations in the order of importance, so you * can freely declare register variables in sub-blocks of code and as * function parameters. Do not use Reg<n> more than once per routine. */#define Reg1 $reg1 /**/#define Reg2 $reg2 /**/#define Reg3 $reg3 /**/#define Reg4 $reg4 /**/#define Reg5 $reg5 /**/#define Reg6 $reg6 /**/#define Reg7 $reg7 /**/#define Reg8 $reg8 /**/#define Reg9 $reg9 /**/#define Reg10 $reg10 /**/#define Reg11 $reg11 /**/#define Reg12 $reg12 /**/#define Reg13 $reg13 /**/#define Reg14 $reg14 /**/#define Reg15 $reg15 /**/#define Reg16 $reg16 /**//* VOIDFLAGS: * This symbol indicates how much support of the void type is given by this * compiler. What various bits mean: * * 1 = supports declaration of void * 2 = supports arrays of pointers to functions returning void * 4 = supports comparisons between pointers to void functions and * addresses of void functions * * The package designer should define VOIDUSED to indicate the requirements * of the package. This can be done either by #defining VOIDUSED before * including config.h, or by defining defvoidused in Myinit.U. If the * level of void support necessary is not present, defines void to int. */#ifndef VOIDUSED#define VOIDUSED $defvoidused#endif#define VOIDFLAGS $voidflags#if (VOIDFLAGS & VOIDUSED) != VOIDUSED#$define void int /* is void to be avoided? */#$define M_VOID /* Xenix strikes again */#endif!GROK!THIS!
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -