Next:Host Misc, Previous:Host Common, Up:Host Configuration [Contents][Index]
GCC needs to know a number of things about the semantics of the hostmachine’s filesystem. Filesystems with Unix and MS-DOS semantics areautomatically detected. For other systems, you can define thefollowing macros inxm-machine.h.
HAVE_DOS_BASED_FILE_SYSTEM ¶This macro is automatically defined bysystem.h if the hostfile system obeys the semantics defined by MS-DOS instead of Unix.DOS file systems are case insensitive, file specifications may beginwith a drive letter, and both forward slash and backslash (‘/’and ‘\’) are directory separators.
DIR_SEPARATOR ¶DIR_SEPARATOR_2 ¶If defined, these macros expand to character constants specifyingseparators for directory names within a file specification.system.h will automatically give them appropriate values onUnix and MS-DOS file systems. If your file system is neither ofthese, define one or both appropriately inxm-machine.h.
However, operating systems like VMS, where constructing a pathname ismore complicated than just stringing together directory namesseparated by a special character, should not define either of thesemacros.
PATH_SEPARATOR ¶If defined, this macro should expand to a character constantspecifying the separator for elements of search paths. The defaultvalue is a colon (‘:’). DOS-based systems usually, but notalways, use semicolon (‘;’).
VMS ¶Define this macro if the host system is VMS.
HOST_OBJECT_SUFFIX ¶Define this macro to be a C string representing the suffix for objectfiles on your host machine. If you do not define this macro, GCC willuse ‘.o’ as the suffix for object files.
HOST_EXECUTABLE_SUFFIX ¶Define this macro to be a C string representing the suffix forexecutable files on your host machine. If you do not define this macro,GCC will use the null string as the suffix for executable files.
HOST_BIT_BUCKET ¶A pathname defined by the host operating system, which can be opened asa file and written to, but all the information written is discarded.This is commonly known as abit bucket ornull device. Ifyou do not define this macro, GCC will use ‘/dev/null’ as the bitbucket. If the host does not support a bit bucket, define this macro toan invalid filename.
UPDATE_PATH_HOST_CANONICALIZE (path) ¶If defined, a C statement (sans semicolon) that performs host-dependentcanonicalization when a path used in a compilation driver orpreprocessor is canonicalized.path is a malloc-ed path to becanonicalized. If the C statement does canonicalizepath into adifferent buffer, the old path should be freed and the new buffer shouldhave been allocated with malloc.
DUMPFILE_FORMAT ¶Define this macro to be a C string representing the format to use forconstructing the index part of debugging dump file names. The resultantstring must fit in fifteen bytes. The full filename will be theconcatenation of: the prefix of the assembler file name, the stringresulting from applying this format to an index number, and a stringunique to each dump file kind, e.g. ‘rtl’.
If you do not define this macro, GCC will use ‘.%02d.’. You shoulddefine this macro if using the default will create an invalid file name.
DELETE_IF_ORDINARY ¶Define this macro to be a C statement (sans semicolon) that performshost-dependent removal of ordinary temp files in the compilation driver.
If you do not define this macro, GCC will use the default version. Youshould define this macro if the default version does not reliably removethe temp file as, for example, on VMS which allows multiple versionsof a file.
HOST_LACKS_INODE_NUMBERS ¶Define this macro if the host filesystem does not report meaningful inodenumbers in struct stat.
Next:Host Misc, Previous:Host Common, Up:Host Configuration [Contents][Index]