This section lists errors that occur when the compiler is processing the command line or handling the configuration files.
You can specify only one source file on the command line. The last one will be compiled,
others will be ignored. This may indicate that you forgot a ’-’ sign.
This option can only be specified when you’re compiling for OS/2.
You cannot nest response files with the @file command line option.
The compiler expects a source file name on the command line.
Displayed when you have notes turned on, and the compiler switches to another options
file.
If you specify -CD for the dos platform, this message is displayed. The compiler
supports only static libraries under dos.
The #IF(N)DEF statements in the options file are not balanced with the #ENDIF
statements.
The #IF(N)DEF statements in the options file are not balanced with the #ENDIF
statements.
The #IF(N)DEF statements in the options file are not balanced with the #ENDIF
statements.
It is possible to have a compiler executable that doesn’t support the generation of
debugging info. If you use such an executable with the -g switch, this warning will be
displayed.
It is possible to have a compiler executable that doesn’t support the generation of
debugging info. If you use such an executable with the -g switch, this warning will be
displayed.
This warns you when you use a switch that is not needed/supported anymore. It is
recommended that you remove the switch to overcome problems in the future, when
the meaning of the switch may change.
This warns you when you use a switch that is not supported anymore. You must
now use the second switch instead. It is recommended that you change the switch to
overcome problems in the future, when the meaning of the switch may change.
This notifies you that the assembler has been changed because you used the -a switch,
which cannot be used with a binary assembler writer.
This notifies you that the assembler has been changed because the binary assembler
writer is not yet ready for cross-endian configuration.
The assembler output selected cannot generate object files with the correct format.
Therefore, the default assembler for this target is used instead.
Message shown when help is shown page per page. When pressing the ENTER Key,
the next page of help is shown. If you press q and then ENTER, the compiler exits.
The compiler is interpreting an option which it read from the configuration file.
Additional information about options. Displayed when you have the debug option
turned on.
An unknown codepage for the source files was requested. The compiler is compiled
with support for several codepages built-in. The requested codepage is not in that list.
You will need to recompile the compiler with support for the codepage you need.
The selected assembler output cannot generate debugging information, debugging
option is therefore disabled.
Using ppc386.cfg is still supported for historical reasons, however, for a multiplatform
system the naming makes no sense anymore. Please continue to use fpc.cfg instead.
An #ELSE statement was found in the options file without a matching #IF(N)DEF
statement.
Not all options are supported or implemented for all target platforms. This message
informs you that a chosen option is incompatible with the currently selected target
platform.
Not all features are supported or implemented for all target platforms. This message
informs you that a chosen feature is incompatible with the currently selected target
platform.
Smart linking is currently incompatible with DWARF debug information on most
platforms, so smart linking is disabled in such cases.
Not all options are supported or implemented for all target platforms. This message
informs you that a chosen option is ignored for the currently selected target platform.
Not all debug formats can be stored in an external file on all platforms. In particular,
on Mac OS X only DWARF debug information can be stored externally.
Smart linking is currently incompatble with DWARF debug information on most
platforms, so smart linking is disabled in such cases.
On Mac OS X,
the MACOSX_DEPLOYMENT_TARGET/IPHONEOS_DEPLOYMENT_TARGET
environment variable can be used to set the default target OS version. In case of Mac
OS X, it has to be of the format XY.Z or XY.Z.AB with X, Y,Z , A and B all digits
from 0-9. In case of iOS, it has to be X.Z.A, where X, Z and A can all be either 1 or 2
digits from 0-9.
The EABIHF (VFP hardfloat) ABI target can only be used with VFP FPUs.
Not all targets support all debug formats (in particular, Stabs is not supported on 64
bit targets).
Do not enable experimental -gc option if -Ur option is given.
The compiler binary only supports a single target architecture. Invoke the fpc binary
if you wish to select a compiler binary for a different target architecture.
The ppc¡target¿ executables support only a single target architecture. They do not
support the -P switch. The compiler driver ”fpc” handles this switch, so you have to
invoke compiling by using ”fpc” instead
To selected a certain feature, the system unit must be compiled with this feature
enabled. All other units inherited the features set by the system unit through the ppu
of the system unit.
Not all instruction sets support all FPU types. For example on ARM, Thumb(-1)
supports no FPU/VFP instruction set
Only one WebAssembly
exception support mode (NOEXCEPTIONS, JSEXCEPTIONS, BFEXCEPTIONS or
NATIVEEXCEPTIONS) can be specified.
Displayed if more than one -t option is specified.