diff --git a/Makefile.am b/Makefile.am index bcbe25a..a1c8a7c 100644 --- a/Makefile.am +++ b/Makefile.am @@ -1,7 +1,7 @@ NULL = SUBDIRS = src lib scm scripts -DIST_SUBDIRS = $(SUBDIRS) autotools config debian doc examples util +DIST_SUBDIRS = $(SUBDIRS) autotools debian doc examples util EXTRA_DIST = \ CONTRIBUTORS \ diff --git a/config/386pc-bsdi-gcc b/config/386pc-bsdi-gcc deleted file mode 100644 index 52a65de..0000000 --- a/config/386pc-bsdi-gcc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=386pc-bsdi-gcc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=bsd - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format= - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=ld - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=yes - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=_ - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size= - file_text_start='N_TXTOFF(hdr)' - mem_text_start='N_TXTADDR(hdr)' - text_length_adj=0 - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=fpurge -flush_tty=tiocflush - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=arg4 - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=no -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=yes - - -# The C compiler used to compile the source code. - -cc=gcc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O2' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime= -vfork=yes -gethostname=yes -uname= -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=yes -utime_h=yes -regcomp=yes - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=int diff --git a/config/Makefile.am b/config/Makefile.am deleted file mode 100644 index e69de29..0000000 diff --git a/config/alpha-osf1-cc b/config/alpha-osf1-cc deleted file mode 100644 index 6b10f1d..0000000 --- a/config/alpha-osf1-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=alpha-osf1-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=no-standard-return-type - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=no - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=yes - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=ecoff - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=dl - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared="-shared -expect_unresolved '*'" - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags= - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=1024 - file_text_start=1024 - mem_text_start=0 - text_length_adj=0 - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tiocflush - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=siginfo - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=yes - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-std1' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=yes -uname=no -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=yes -utime_h=yes -regcomp=yes - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/dec5100-ultrix4.2-cc b/config/dec5100-ultrix4.2-cc deleted file mode 100644 index 81a2eda..0000000 --- a/config/dec5100-ultrix4.2-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=dec5100-ultrix4.2-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=no - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=bsd - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=ecoff - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=ld - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc_G0' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags= - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h='' - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=yes - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=sigcontext - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags=-D_NO_PROTO - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags='-G 0' - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags='-G 0' - - -# The linker flags used to link the interpreter. - -ldflags='-lm -Wl,-D,800000' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=no - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=no -utime_h=yes -regcomp=no - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=int diff --git a/config/hp9k700-hpux10.0-cc b/config/hp9k700-hpux10.0-cc deleted file mode 100644 index 2055467..0000000 --- a/config/hp9k700-hpux10.0-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=hp9k700-hpux10.0-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=no - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=no - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=no -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=no -sysconf_pagesize=yes - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=hp9k - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=shl - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries= - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size= - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size='(1024*1024)' - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=hpux - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=no - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h= -pragma_alloca= - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=yes - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-Ae -O -DARRAY_BROKEN' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags=+z - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-Wl,-E -lm -ldld' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=no -wait4=no -utime_h=yes -regcomp=yes - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/hp9k700-hpux9.0-cc b/config/hp9k700-hpux9.0-cc deleted file mode 100644 index b91b1c4..0000000 --- a/config/hp9k700-hpux9.0-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=hp9k700-hpux9.0-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=no - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=no - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=no - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=no -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=no -sysconf_pagesize=yes - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=hp9k - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=shl - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries= - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size= - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size='(1024*1024)' - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=hpux - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=no - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h= -pragma_alloca= - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=yes - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-Ae -O -DARRAY_BROKEN' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags=+z - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-Wl,-E -lm -ldld' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=no -rename=yes -waitpid=yes -wait3=no -wait4=no -utime_h=yes -regcomp=yes - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/i486-linux-gcc b/config/i486-linux-gcc deleted file mode 100644 index 0dffefa..0000000 --- a/config/i486-linux-gcc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=i486-linux-gcc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=no - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=no - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include= - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=no -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format= - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=ld - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc -lgcc -lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags="-x -static" - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h='' - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=yes - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=_ - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=1024 - file_text_start='N_TXTOFF(hdr)' - mem_text_start='0' - text_length_adj='0' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize=4096 - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio= -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=no - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr= - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc='gcc' - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O2' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-static -lm' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=yes - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=no -uname=yes -mktemp=yes -tmpnam=yes -tempnam= -getcwd=yes -getwd= -rename=yes -waitpid=yes -wait3= -wait4=yes -utime_h=yes -regcomp=yes - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/next-mach3.3-cc b/config/next-mach3.3-cc deleted file mode 100644 index 6fdfa09..0000000 --- a/config/next-mach3.3-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=next-mach3.3-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=no - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=no - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=no - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=no - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=bsd - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=macho - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=rld - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='/lib/libsys_s.a' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=_ - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=no - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tiocflush - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=no - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr= - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=no -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-seglinkedit -lm' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=yes -uname=no -mktemp=yes -tmpnam=yes -tempnam=no -getcwd=no -getwd=yes -rename=yes -waitpid=no -wait3=yes -wait4=yes -utime_h=no -regcomp=no - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=int diff --git a/config/powerpc-aix4.1-gcc b/config/powerpc-aix4.1-gcc deleted file mode 100644 index c4a0191..0000000 --- a/config/powerpc-aix4.1-gcc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=power-aix4.1-gcc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize= - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=xcoff - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj= - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=. - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=no - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize=4096 - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=aix - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=no -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=gcc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags=-O - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lld -lm' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=yes - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=no -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=no -utime_h=yes -regcomp=yes - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/powerpc-aix4.1-xlc b/config/powerpc-aix4.1-xlc deleted file mode 100644 index d48fdac..0000000 --- a/config/powerpc-aix4.1-xlc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=power-aix4.1-xlc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize= - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=xcoff - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj= - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=. - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=no - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize=4096 - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=aix - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=no -pragma_alloca=yes - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags=-O - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lld -lm' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=yes - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=no -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=no -utime_h=yes -regcomp=yes - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/powerpc-solaris2.5-cc b/config/powerpc-solaris2.5-cc deleted file mode 100644 index 87500bb..0000000 --- a/config/powerpc-solaris2.5-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=powerpc-solaris2.5-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=no - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=no - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=yes - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=elf - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=dl - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared="-G -z text" - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries= - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags= - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=yes - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=siginfo - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=yes - - -# The C compiler used to compile the source code. - -cc=/opt/SUNWspro/bin/cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=/usr/ccs/bin/ld - - -# The C compiler flags used for all files. - -cflags='-O' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags='-K PIC' - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm -lelf -ldl' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=yes - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=no -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=yes -utime_h=yes -regcomp=yes - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/rs6000-aix3.2-cc b/config/rs6000-aix3.2-cc deleted file mode 100644 index 2abf859..0000000 --- a/config/rs6000-aix3.2-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=rs6000-aix3.2-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize= - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=bsd - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=xcoff - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj= - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=. - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=no - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize=4096 - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect= - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=aix - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=no -pragma_alloca=yes - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags= - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lld -lm' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=yes - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=no -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=no -utime_h=yes -regcomp=yes - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/sgi-irix5.3-cc b/config/sgi-irix5.3-cc deleted file mode 100644 index e588699..0000000 --- a/config/sgi-irix5.3-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=sgi-irix5.3-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max= - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=no -sysconf_pagesize=yes - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=elf - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=dl - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared="-shared" - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries= - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags= - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=yes - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=siginfo - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm -lelf' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=no -vfork=no -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=no -utime_h=yes -regcomp=no - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/sgi-irix6.2-cc b/config/sgi-irix6.2-cc deleted file mode 100644 index b5dfa61..0000000 --- a/config/sgi-irix6.2-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=sgi-irix6.2-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max= - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=yes - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=elf - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=dl - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared="-shared -dont_warn_unused" - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries= - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags= - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=yes - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=siginfo - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm -lelf' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=no -vfork=no -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=no -utime_h=yes -regcomp=yes - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/site b/config/site deleted file mode 100644 index 183ac05..0000000 --- a/config/site +++ /dev/null @@ -1,82 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather site- and installation-specific -# information required for building the Makefiles. -# -# This script is read after the "system" file, therefore you can place -# variable settings here to override those from "system". -# -# Some variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# The directory where all files are installed by running "make install". -# The subdirectories bin, lib, include, and runtime (with various -# subdirectories) are created automatically, but $install_dir isn't. -# Make sure $install_dir doesn't point to the top of the source tree -# (i.e. choose a subdirectory or a directory outside the source tree). - -install_dir='$(DESTDIR)'/usr -final_dir=/usr - - -# Libraries against which to link the X11 extension (typically -lX11). -# -# Any of the following library lists may be prefixed by something like -# -L/usr/X11/lib if the X-libraries do not reside in a standard directory; -# an additional -R/usr/X11/lib and -lsocket may be required in case of -# SunOS 5.x/SysVR4). - -libxlib='-L/usr/X11R6/lib -lX11' - - -# Libraries against which to link the Xt extension (typically -# -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11). -lXaw is needed to get the -# correct definition of the vendor shell widget class - -libxt='-L/usr/X11R6/lib -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11' - - -# Libraries against which to link the Athena widgets extension (typically -# identical to libxt above) - -libxaw='-L/usr/X11R6/lib -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11' - - -# Libraries against which to link the Motif extension (typically like -# libaw above with Xaw replaced by Xm) - -libxmotif='-L/usr/X11R6/lib -lXm -lXmu -lXt -lSM -lICE -lXext -lX11' - - -# Additional flags (typically -Isomething) to be supplied to the C -# compiler when compiling an X11 application, or a Motif application, -# respectively. - -x11_incl=-I/usr/X11R6/include -motif_incl=-I/usr/include/Xm - - -# Set "gdbm" to "yes" if you have the GNU gdbm library installed and -# want the gdbm extension to be compiled. "gdbm_inc" gives additional -# C compiler flags required to compile a program using gdbm. - -gdbm=yes -gdbm_incl= - - -# Do you want to use the generational garbage collector? If not, the -# stop-and-copy garbage collector will be used. - -generational_gc=yes - - -# The default heap size of the Scheme interpreter in KBytes (if the -# stop-and-copy garbage collector is used). - -default_heap_size=1024 diff --git a/config/sites/alpha-osf1 b/config/sites/alpha-osf1 deleted file mode 100644 index fa22d7c..0000000 --- a/config/sites/alpha-osf1 +++ /dev/null @@ -1,81 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather site- and installation-specific -# information required for building the Makefiles. -# -# This script is read after the "system" file, therefore you can place -# variable settings here to override those from "system". -# -# Some variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# The directory where all files are installed by running "make install". -# The subdirectories bin, lib, include, and runtime (with various -# subdirectories) are created automatically, but $install_dir isn't. -# Make sure $install_dir doesn't point to the top of the source tree -# (i.e. choose a subdirectory or a directory outside the source tree). - -install_dir=/user/net/elk - - -# Libraries against which to link the X11 extension (typically -lX11). -# -# Any of the following library lists may be prefixed by something like -# -L/usr/X11/lib if the X-libraries do not reside in a standard directory; -# an additional -R/usr/X11/lib and -lsocket may be required in case of -# SunOS 5.x/SysVR4). - -libxlib='-lX11' - - -# Libraries against which to link the Xt extension (typically -# -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11). -lXaw is needed to get the -# correct definition of the vendor shell widget class - -libxt='-lXaw -lXmu -lXt -lXext -lX11' - - -# Libraries against which to link the Athena widgets extension (typically -# identical to libxt above) - -libxaw='-lXaw -lXmu -lXt -lXext -lX11' - - -# Libraries against which to link the Motif extension (typically like -# libaw above with Xaw replaced by Xm) - -libxmotif='-lXm -lXmu -lXt -lXext -lX11' - - -# Additional flags (typically -Isomething) to be supplied to the C -# compiler when compiling an X11 application, or a Motif application, -# respectively. - -x11_incl= -motif_incl= - - -# Set "gdbm" to "yes" if you have the GNU gdbm library installed and -# want the gdbm extension to be compiled. "gdbm_inc" gives additional -# C compiler flags required to compile a program using gdbm. - -gdbm= -gdbm_incl="-I/usr/gnu/include/gdbm" - - -# Do you want to use the generational garbage collector? If not, the -# stop-and-copy garbage collector will be used. - -generational_gc=yes - - -# The default heap size of the Scheme interpreter in KBytes (if the -# stop-and-copy garbage collector is used). - -default_heap_size=1024 diff --git a/config/sites/dec5100-ultrix b/config/sites/dec5100-ultrix deleted file mode 100644 index 0b8b866..0000000 --- a/config/sites/dec5100-ultrix +++ /dev/null @@ -1,81 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather site- and installation-specific -# information required for building the Makefiles. -# -# This script is read after the "system" file, therefore you can place -# variable settings here to override those from "system". -# -# Some variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# The directory where all files are installed by running "make install". -# The subdirectories bin, lib, include, and runtime (with various -# subdirectories) are created automatically, but $install_dir isn't. -# Make sure $install_dir doesn't point to the top of the source tree -# (i.e. choose a subdirectory or a directory outside the source tree). - -install_dir=/usr/local/elk - - -# Libraries against which to link the X11 extension (typically -lX11). -# -# Any of the following library lists may be prefixed by something like -# -L/usr/X11/lib if the X-libraries do not reside in a standard directory; -# an additional -R/usr/X11/lib and -lsocket may be required in case of -# SunOS 5.x/SysVR4). - -libxlib='-L/usr/local/X11/lib -lX11_G0' - - -# Libraries against which to link the Xt extension (typically -# -lXaw -lXmu -lXt -lXext -lX11). -lXaw is needed to get the correct -# definition of the vendor shell widget class - -libxt='-L/usr/local/X11/lib -lXaw_G0 -lXmu_G0 -lXt_G0 -lXext_G0 -lX11_G0' - - -# Libraries against which to link the Athena widgets extension (typically -# identical to libxt above) - -libxaw='-L/usr/local/X11/lib -lXaw_G0 -lXmu_G0 -lXt_G0 -lXext_G0 -lX11_G0' - - -# Libraries against which to link the Motif extension (typically like -# libaw above with Xaw replaced by Xm) - -libxmotif='-L/usr/local/X11/lib -lXm_G0 -lXmu_G0 -lXt_G0 -lXext_G0 -lX11_G0' - - -# Additional flags (typically -Isomething) to be supplied to the C -# compiler when compiling an X11 application, or a Motif application, -# respectively. - -x11_incl= -motif_incl= - - -# Set "gdbm" to "yes" if you have the GNU gdbm library installed and -# want the gdbm extension to be compiled. "gdbm_inc" gives additional -# C compiler flags required to compile a program using gdbm. - -gdbm= -gdbm_incl="-I/usr/gnu/include/gdbm" - - -# Do you want to use the generational garbage collector? If not, the -# stop-and-copy garbage collector will be used. - -generational_gc=yes - - -# The default heap size of the Scheme interpreter in KBytes (if the -# stop-and-copy garbage collector is used). - -default_heap_size=1024 diff --git a/config/sites/hp9k700-hpux9.0 b/config/sites/hp9k700-hpux9.0 deleted file mode 100644 index e0df5a7..0000000 --- a/config/sites/hp9k700-hpux9.0 +++ /dev/null @@ -1,81 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather site- and installation-specific -# information required for building the Makefiles. -# -# This script is read after the "system" file, therefore you can place -# variable settings here to override those from "system". -# -# Some variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# The directory where all files are installed by running "make install". -# The subdirectories bin, lib, include, and runtime (with various -# subdirectories) are created automatically, but $install_dir isn't. -# Make sure $install_dir doesn't point to the top of the source tree -# (i.e. choose a subdirectory or a directory outside the source tree). - -install_dir=/usr/local/elk - - -# Libraries against which to link the X11 extension (typically -lX11). -# -# Any of the following library lists may be prefixed by something like -# -L/usr/X11/lib if the X-libraries do not reside in a standard directory; -# an additional -R/usr/X11/lib and -lsocket may be required in case of -# SunOS 5.x/SysVR4). - -libxlib=/usr/lib/X11R5/libX11.sl - - -# Libraries against which to link the Xt extension (typically -# -lXaw -lXmu -lXt -lXext -lX11). -lXaw is needed to get the correct -# definition of the vendor shell widget class - -libxt='/usr/lib/X11R5/libXt.sl /usr/lib/X11R5/libX11.sl' - - -# Libraries against which to link the Athena widgets extension (typically -# identical to libxt above) - -libxaw= - - -# Libraries against which to link the Motif extension (typically like -# libaw above with Xaw replaced by Xm) - -libxmotif='/usr/lib/Motif1.2/libXm.sl /usr/lib/X11R5/libXt.sl /usr/lib/X11R5/libX11.sl' - - -# Additional flags (typically -Isomething) to be supplied to the C -# compiler when compiling an X11 application, or a Motif application, -# respectively. - -x11_incl=-I/usr/include/X11R5 -motif_incl=-I/usr/include/Motif1.2 - - -# Set "gdbm" to "yes" if you have the GNU gdbm library installed and -# want the gdbm extension to be compiled. "gdbm_inc" gives additional -# C compiler flags required to compile a program using gdbm. - -gdbm= -gdbm_incl="-I/usr/gnu/include/gdbm" - - -# Do you want to use the generational garbage collector? If not, the -# stop-and-copy garbage collector will be used. - -generational_gc=yes - - -# The default heap size of the Scheme interpreter in KBytes (if the -# stop-and-copy garbage collector is used). - -default_heap_size=1024 diff --git a/config/sites/sun-sunos4.1 b/config/sites/sun-sunos4.1 deleted file mode 100644 index 27f7e72..0000000 --- a/config/sites/sun-sunos4.1 +++ /dev/null @@ -1,81 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather site- and installation-specific -# information required for building the Makefiles. -# -# This script is read after the "system" file, therefore you can place -# variable settings here to override those from "system". -# -# Some variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# The directory where all files are installed by running "make install". -# The subdirectories bin, lib, include, and runtime (with various -# subdirectories) are created automatically, but $install_dir isn't. -# Make sure $install_dir doesn't point to the top of the source tree -# (i.e. choose a subdirectory or a directory outside the source tree). - -install_dir=/usr/local/elk - - -# Libraries against which to link the X11 extension (typically -lX11). -# -# Any of the following library lists may be prefixed by something like -# -L/usr/X11/lib if the X-libraries do not reside in a standard directory; -# an additional -R/usr/X11/lib and -lsocket may be required in case of -# SunOS 5.x/SysVR4). - -libxlib='-L/usr/local/X11/lib -lX11' - - -# Libraries against which to link the Xt extension (typically -# -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11). -lXaw is needed to get the -# correct definition of the vendor shell widget class - -libxt='-L/usr/local/X11/lib -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11' - - -# Libraries against which to link the Athena widgets extension (typically -# identical to libxt above) - -libxaw='-L/usr/local/X11/lib -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11' - - -# Libraries against which to link the Motif extension (typically like -# libaw above with Xaw replaced by Xm) - -libxmotif='-L/usr/local/X11/lib -lXm -lXmu -lXt -lSM -lICE -lXext -lX11' - - -# Additional flags (typically -Isomething) to be supplied to the C -# compiler when compiling an X11 application, or a Motif application, -# respectively. - -x11_incl= -motif_incl= - - -# Set "gdbm" to "yes" if you have the GNU gdbm library installed and -# want the gdbm extension to be compiled. "gdbm_inc" gives additional -# C compiler flags required to compile a program using gdbm. - -gdbm= -gdbm_incl="-I/usr/gnu/include/gdbm" - - -# Do you want to use the generational garbage collector? If not, the -# stop-and-copy garbage collector will be used. - -generational_gc=yes - - -# The default heap size of the Scheme interpreter in KBytes (if the -# stop-and-copy garbage collector is used). - -default_heap_size=1024 diff --git a/config/sites/sun-sunos5 b/config/sites/sun-sunos5 deleted file mode 100644 index 30882e5..0000000 --- a/config/sites/sun-sunos5 +++ /dev/null @@ -1,81 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather site- and installation-specific -# information required for building the Makefiles. -# -# This script is read after the "system" file, therefore you can place -# variable settings here to override those from "system". -# -# Some variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# The directory where all files are installed by running "make install". -# The subdirectories bin, lib, include, and runtime (with various -# subdirectories) are created automatically, but $install_dir isn't. -# Make sure $install_dir doesn't point to the top of the source tree -# (i.e. choose a subdirectory or a directory outside the source tree). - -install_dir=/usr/local/elk - - -# Libraries against which to link the X11 extension (typically -lX11). -# -# Any of the following library lists may be prefixed by something like -# -L/usr/X11/lib if the X-libraries do not reside in a standard directory; -# an additional -R/usr/X11/lib and -lsocket may be required in case of -# SunOS 5.x/SysVR4). - -libxlib='-R/usr/local/X11/lib -L/usr/local/X11/lib -lX11 -lsocket' - - -# Libraries against which to link the Xt extension (typically -# -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11). -lXaw is needed to get the -# correct definition of the vendor shell widget class - -libxt='-R/usr/local/X11/lib -L/usr/local/X11/lib -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11 -lsocket' - - -# Libraries against which to link the Athena widgets extension (typically -# identical to libxt above) - -libxaw='-R/usr/local/X11/lib -L/usr/local/X11/lib -lXaw -lXmu -lXt -lSM -lICE -lXext -lX11 -lsocket' - - -# Libraries against which to link the Motif extension (typically like -# libaw above with Xaw replaced by Xm) - -libxmotif='-R/usr/local/X11/lib -L/usr/local/X11/lib -lXm -lXmu -lXt -lXext -lSM -lICE -lX11 -lsocket' - - -# Additional flags (typically -Isomething) to be supplied to the C -# compiler when compiling an X11 application, or a Motif application, -# respectively. - -x11_incl=-I/usr/local/X11/include -motif_incl=-I/usr/local/X11/include - - -# Set "gdbm" to "yes" if you have the GNU gdbm library installed and -# want the gdbm extension to be compiled. "gdbm_inc" gives additional -# C compiler flags required to compile a program using gdbm. - -gdbm= -gdbm_incl="-I/usr/gnu/include/gdbm" - - -# Do you want to use the generational garbage collector? If not, the -# stop-and-copy garbage collector will be used. - -generational_gc=yes - - -# The default heap size of the Scheme interpreter in KBytes (if the -# stop-and-copy garbage collector is used). - -default_heap_size=1024 diff --git a/config/sun-sunos4.1-acc b/config/sun-sunos4.1-acc deleted file mode 100644 index e074ad5..0000000 --- a/config/sun-sunos4.1-acc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=sun-sunos4.1-acc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=bsd - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format= - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=ld - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=_ - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=arg4 - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=yes - - -# The C compiler used to compile the source code. - -cc=acc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O -Xa' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm -Bstatic' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=yes - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=yes -utime_h=yes -regcomp=no - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=int diff --git a/config/sun-sunos4.1-cc b/config/sun-sunos4.1-cc deleted file mode 100644 index 6a8cfc7..0000000 --- a/config/sun-sunos4.1-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=sun-sunos4.1-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=bsd - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format= - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=ld - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=_ - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=arg4 - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags=-D_NO_PROTO - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm -Bstatic' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=no - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=yes -utime_h=yes -regcomp=no - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=int diff --git a/config/sun-sunos4.1-gcc b/config/sun-sunos4.1-gcc deleted file mode 100644 index 37d77d9..0000000 --- a/config/sun-sunos4.1-gcc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=sun-sunos4.1-gcc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=bsd - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format= - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=ld - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=_ - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=arg4 - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=yes - - -# The C compiler used to compile the source code. - -cc=gcc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-ansi -O -fschedule-insns2' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm -static' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=yes -utime_h=yes -regcomp=no - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=int diff --git a/config/sun-sunos5-acc b/config/sun-sunos5-acc deleted file mode 100644 index 7839a19..0000000 --- a/config/sun-sunos5-acc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=sun-sunos5-acc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=no - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=no - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=no - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=no -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=no -sysconf_pagesize=yes - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=elf - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=dl - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared="-G -z text" - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries= - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags= - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=siginfo - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=yes - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=/usr/ccs/bin/ld - - -# The C compiler flags used for all files. - -cflags='-O -Xa -D__svr4__' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags='-K PIC' - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm -lelf -ldl' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=yes - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=no -vfork=yes -gethostname=no -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=no -rename=yes -waitpid=yes -wait3=no -wait4=no -utime_h=yes -regcomp=no - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/sun-sunos5-gcc b/config/sun-sunos5-gcc deleted file mode 100644 index 56a182d..0000000 --- a/config/sun-sunos5-gcc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=sun-sunos5-gcc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=no - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=no - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=no - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=no -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=no -sysconf_pagesize=yes - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=elf - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=dl - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared="-G -z text" - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries= - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags= - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=siginfo - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=yes - - -# The C compiler used to compile the source code. - -cc=gcc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=/usr/ccs/bin/ld - - -# The C compiler flags used for all files. - -cflags='-O -fschedule-insns2' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags='-fpic' - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm -lelf -ldl' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=no -vfork=yes -gethostname=no -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=no -rename=yes -waitpid=yes -wait3=no -wait4=no -utime_h=yes -regcomp=no - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/system b/config/system deleted file mode 100644 index 9d2c582..0000000 --- a/config/system +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=i486-linux-gcc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include="" - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=elf - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=dl - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared=-shared - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries= - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags="-x -static" - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h='' - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=yes - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=1024 - file_text_start='N_TXTOFF(hdr)' - mem_text_start='0' - text_length_adj='0' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize=4096 - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio= -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=no - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr= - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc='gcc' - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-g -Wall -O2 -I/usr/include/libelf' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags=-fPIC - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-rdynamic -lm -ldl -lelf' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=yes - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=yes -utime_h=yes -regcomp=yes - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/untested/386pc-386bsd-gcc b/config/untested/386pc-386bsd-gcc deleted file mode 100644 index 5d322f9..0000000 --- a/config/untested/386pc-386bsd-gcc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=386pc-386bsd-gcc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=bsd - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format= - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=ld - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=yes - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=_ - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=4096 - file_text_start=4096 - mem_text_start=0 - text_length_adj=0 - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=fpurge -flush_tty=tiocflush - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=arg4 - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=no -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=yes - - -# The C compiler used to compile the source code. - -cc=gcc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-Di386 -O' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime= -vfork=yes -gethostname=yes -uname= -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=yes -utime_h=yes -regcomp=no - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=int diff --git a/config/untested/386pc-dos-gcc b/config/untested/386pc-dos-gcc deleted file mode 100644 index c630321..0000000 --- a/config/untested/386pc-dos-gcc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=386pc-dos-gcc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include= - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals= - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format= - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=ld - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags=-x - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=yes - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=_ - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=yes - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGMENT_SIZE - file_text_start='sizeof(struct exec)' - mem_text_start='(4096+sizeof(struct exec))' - text_length_adj=0 - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty= - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size='(512*1024)' - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=no - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=arg4 - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=no -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=gcc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday= -ftime= -vfork=no -gethostname= -uname= -mktemp= -tmpnam= -tempnam= -getcwd= -getwd= -rename= -waitpid= -wait3= -wait4= -utime_h= -regcomp= - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=int diff --git a/config/untested/convex230-convexos10-cc b/config/untested/convex230-convexos10-cc deleted file mode 100644 index a4b207c..0000000 --- a/config/untested/convex230-convexos10-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=convex230-convexos10-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=bsd - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=convex - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj= - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags= - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with=_ - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=no - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=1024 - file_text_start=1024 - mem_text_start=0 - text_length_adj=0 - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=no - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tiocflush - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=no - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr= - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=yes - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=no -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=yes - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=yes -uname=yes -mktemp=yes -tmpnam=yes -tempnam=no -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=yes -wait4=no -utime_h=yes -regcomp= - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/untested/cray-unicos-cc b/config/untested/cray-unicos-cc deleted file mode 100644 index 9cc6f1d..0000000 --- a/config/untested/cray-unicos-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=cray-unicos-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=no - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include= - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=no - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=no -sysconf_pagesize=yes - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format= - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj= - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared="-G -z text" - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries= - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags= - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=no - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio= -flush_tty= - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size=2000000 - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=yes - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr=siginfo - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=no - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h=yes -pragma_alloca=no - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=yes - - -# The C compiler used to compile the source code. - -cc=cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=/usr/ccs/bin/ld - - -# The C compiler flags used for all files. - -cflags='-O ' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags='-K PIC' - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm -lelf -ldl' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=yes - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=no -vfork=yes -gethostname=no -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=yes -rename=yes -waitpid=yes -wait3=no -wait4=no -utime_h=yes -regcomp= - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/untested/mx300i-svr4-cc b/config/untested/mx300i-svr4-cc deleted file mode 100644 index f8f2168..0000000 --- a/config/untested/mx300i-svr4-cc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=mx300i-svr4-cc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=no - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=no - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=no - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=yes - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=no -sysconf_open_max=yes - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=yes - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=no -sysconf_pagesize=yes - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=posix - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=elf - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj= - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags= - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h=unused - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=yes - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tcflsh - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=no - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr= - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=no - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h= -pragma_alloca= - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=/usr/ccs/bin/cc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags=-D_NO_PROTO - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-dn -lm -lelf' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=yes - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=no -vfork=yes -gethostname=no -uname=yes -mktemp=yes -tmpnam=yes -tempnam=yes -getcwd=yes -getwd=no -rename=yes -waitpid=yes -wait3=no -wait4=no -utime_h=yes -regcomp= - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=gid_t diff --git a/config/untested/sony3200-news4-gcc b/config/untested/sony3200-news4-gcc deleted file mode 100644 index 91a1d1d..0000000 --- a/config/untested/sony3200-news4-gcc +++ /dev/null @@ -1,367 +0,0 @@ -# This is a shell script. It is sourced by the build scripts in the -# various subdirectories to gather system-, compiler-, and OS-specific -# information required for building the Makefiles. -# -# Most variables in this script are interpreted as boolean variables and -# indicate presence or absence of one specific feature. The value "yes" -# is regarded as "true", all other values (including no value or even -# non-existence of the variable) are interpreted as "false". -# -# Do not forget to quote values that contain shell meta syntax. -# -# ----------------------------------------------------------------------- - - -# $system should contain the name of this file. It may be used by some -# of the build scripts to do things that are specific to one single -# type of system. - -system=sony3200-news4-gcc - - -# Does the system support the vprintf library function? If not, -# availability of the (non-portable) _doprnt function is assumed. - -vprintf=yes - - -# Does the directory(3) library follow the POSIX conventions (i.e. -# requires the include file and uses "struct dirent")? -# If not, the (obsolete) BSD-style interface with and -# "struct direct" is assumed. - -dirent=yes - - -# Does the system have the random/srandom library functions? If not, -# rand/srand will be used instead. - -random=yes - - -# Does the system have the index library function? If not, strchr -# will be used. - -index=yes - - -# Does the system have the bcopy, bzero, and bcmp library functions? -# If not, memcpy/memset/memcmp will be used. - -bstring=yes - - -# Does using the access system call require to be included? -# (Look into the manual page for access if in doubt.) - -include_unistd_h=no - - -# If the FIONREAD ioctl command is defined, which file must be included? - -fionread_include='' - - -# What is the name of the a.out include file? - -aout_h='' - - -# The following variables control how certain system limits are obtained -# during runtime. -# -# If getdtablesize() is available to determine the maximum number of open -# files per process, set getdtablesize=yes. -# Alternatively, if POSIX-style sysconf() can be called with _SC_OPEN_MAX, -# set sysconf_open_max=yes. -# If neither is set to "yes", an educated guess will be made. - -getdtablesize=yes -sysconf_open_max=no - -# If POSIX-style pathconf() can be invoked with _PC_PATH_MAX to determine -# the maximum pathname length, set pathconf_path_max=yes. - -pathconf_path_max=no - -# If the system page size can be determined by calling getpagesize() -# set getpagesize=yes. -# Alternatively, if sysconf() can be invoked with _SC_PAGESIZE, set -# sysconf_pagesize=yes. -# These two variables are only required if the generational garbage -# collector is used. - -getpagesize=yes -sysconf_pagesize=no - - -# Set reliable_signals=bsd if your system supports BSD-style reliable -# signals (has sigblock and related functions); set reliable_signals=posix -# for POSIX-style signals (sigprocmask, sigsets); otherwise old V7/SysV -# signal semantics are assumed. - -reliable_signals=bsd - - -# To support dynamic loading of object files and "dump", the system's -# a.out format has to be known. Choose one of the following: -# -# coff ecoff xcoff elf macho hp9k convex -# -# Other values of "aout_format" are interpreted as BSD-style a.out format. - -aout_format=ecoff - - -# Which mechanism should be used to dynamically load object files? -# Possible values currently are: -# -# ld BSD-style incremental loading based on ld -A -# rld NeXT-style rld_load() -# shl HP-UX shl_load() -# dl SysVR4/SunOS5 dlopen() -# -# Leave load_obj empty if dynamic loading is not supported. - -load_obj=ld - - - # The following variables are only relevant if load_obj is set. - - # Linker options to produce a shared object from a .o file. - # Only used if load_obj=dl. - - ldflags_shared= - - # The libraries against which dynamically loaded files are resolved - # at the time they are loaded. - - load_libraries='-lc' - - # Additional flags to be passed to the linker for an incremental - # linker run (ld -A). Ignored unless load_obj=ld. - - incremental_ldflags= - - # Systems with "aout_format=ecoff" may require a call to the cacheflush - # system call after an object file has been loaded. Which include file - # has to be included in this case? - - cachectl_h= - - # Is the ANSI-C atexit function supported to register an exit handler? - # If not, the exit library function will be redefined and will end in - # a call to _exit. - - atexit=no - - -# Do the names of external functions in the symbol table always begin -# with a special character (such as underline)? If so, syms_begin_with -# should hold this character, otherwise leave it empty. - -syms_begin_with= - - -# The symbol prefixes of extension initialization and finalization -# functions (without the initial $syms_begin_with). Do not change -# these unless the compiler or linker restricts the length of symbols! - -init_prefix=elk_init_ -finit_prefix=elk_finit_ - - -# Is the "dump" function supported? - -can_dump=no - - -# The following variables are only relevant if "can_dump=yes". - - # Is the fchmod system call broken or unavailable? - - fchmod_broken=no - - # These four variables are only relevant if the system has the BSD-style - # a.out format. - # segment_size is the segment size of the system's memory management - # unit, i.e. the number to a multiple of which the size of an a.out - # segment (e.g. .text) is rounded up. - # file_text_start is the file offset at which the text segment starts - # in an a.out file. - # mem_text_start is the starting address of the text segment in memory. - # text_length_adj must be set to "sizeof (struct exec)" if the length of - # the text segment stored in the a.out header includes the a.out header - # itself. - - segment_size=SEGSIZ - file_text_start='sizeof(struct exec)' - mem_text_start='(PAGSIZ+sizeof(struct exec))' - text_length_adj='sizeof(struct exec)' - - # Only relevant if "aout_format=coff": the system's pagesize. - - coff_pagesize= - - # Only relevant if "aout_format=hp9k" and "load_obj=shl" - - hp_shared_libraries=yes - - # Print debug messages when dumping - - debug_dump=yes - - -# Is the "termio" terminal interface supported by the system? If not, -# BSD-style tty handling will be used. - -termio=yes - - -# flush_stdio and flush_tty indicate how clear-input/output-port can -# flush (purge) a FILE pointer and a TTY file descriptor. -# Possible values of flush_stdio: -# bsd assume old BSD-style FILE* (with _cnt, _ptr, _base) -# fpurge use 4.4BSD-style fpurge stdio library function -# Possible values of flush_tty: -# tiocflush use TIOCFLUSH ioctl from -# tcflsh use TCFLSH ioctl from -# Leave the variable(s) empty if flushing is not supported. - -flush_stdio=bsd -flush_tty=tiocflush - - -# The interpreter uses the getrlimit function to determine the maximum -# stack size of the running program. If this function is not supported, -# set max_stack_size to a (fixed) maximum stack size (in bytes). - -max_stack_size= - - -# Is the mprotect system call supported? The generational garbage collector -# requires mprotect to implement incremental GC. $mprotect is ignored if -# generational_gc is set to "no" in the site file. Set mprotect=mmap if -# mprotect is supported, but only for mmap()ed memory. - -mprotect=no - - -# How can a SIGSEGV or SIGBUS signal handler find out the address of -# the faulting memory reference? This variable is only used if -# $mprotect is "yes" or "mmap". Possible values are: -# -# siginfo handler is called with siginfo_t structure (enabled -# by a call to sigaction) -# sigcontext address is in the sigcontext structure (3rd arg, sc_badvaddr) -# arg4 address is delivered to handler as argument #4 -# aix use an AIX-specific hack to get hold of the bad address -# hpux use a HP-UX-specific hack - -sigsegv_addr= - - -# Does the system support the alloca library function, and does this -# function actually extend the stack? If in doubt, extract alloca.o -# from the C library and check if it contains the symbols malloc and free. -# If this is the case, forget it. - -use_alloca=no - - -# Must be included to use alloca? Is "#pragma alloca" required? - -include_alloca_h= -pragma_alloca= - - -# Does the system (or compiler) require certain objects (e.g. doubles) -# to be aligned at 8-byte boundaries? If not, 4-byte alignment will -# be assumed. - -align_8byte=no - - -# The C compiler used to compile the source code. - -cc=gcc - - -# The name of the linker. This is usually just "ld", or /usr/ccs/bin/ld -# in SVR4-based systems. - -ld=ld - - -# The C compiler flags used for all files. - -cflags='-O -DSEEK_SET=1' - - -# Are extra C compiler flags (such as -D_NO_PROTO) required to compile -# Motif applications? - -motif_cflags= - - -# Are extra C compiler flags (such as -G 0) required to compile -# dynamically loadable files? - -obj_cflags= - - -# Are extra linker flags (such as -G 0) required to link several object -# files together to one dynamically loadable file? - -obj_ldflags= - - -# The linker flags used to link the interpreter. - -ldflags='-lm' - - -# The lint flags. - -lintflags='-abxh' - - -# Are function prototypes in the header files required? If prototypes=yes, -# prototypes are used unconditionally; if prototypes=no, prototypes are -# not used; otherwise prototypes are only used if the source code is -# compiled with an ANSI-C- or C++-compiler. - -prototypes=no - - -# Does your C preprocessor support the ANSI-C ## operator, although -# __STDC__ is not defined? - -ansi_cpp=no - - -# The UNIX extension likes to know which of the following system calls, -# library functions, and include files are supported by the system. - -gettimeofday=yes -ftime=yes -vfork=yes -gethostname=yes -uname=no -mktemp=yes -tmpnam=no -tempnam=no -getcwd=yes -getwd=yes -rename=yes -waitpid=no -wait3=yes -wait4=yes -utime_h=no -regcomp= - - -# Element type of the gidset argument of getgroups(); typically int -# or gid_t. Only needed by the UNIX extension. - -getgroups_type=int