C.11 Command line handling errors

This section lists errors that occur when the compiler is processing the command line or handling the configuration files.

Warning 11001: Only one source file supported, changing source file to compile from ”〈arg. 1〉” into ”〈arg. 2〉”

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.

Warning 11002: DEF file can be created only for OS/2

This option can only be specified when you’re compiling for OS/2.

Error 11003: Nested response files are not supported

You cannot nest response files with the @file command line option.

Fatal error 11004: No source file name in command line

The compiler expects a source file name on the command line.

Note 11005: No option inside 〈arg. 1〉 config file

The compiler didn’t find any option in that config file.

Error 11006: Illegal parameter: 〈arg. 1〉

You specified an unknown option.

Hint 11007: -? writes help pages

When an unknown option is given, this message is displayed.

Fatal error 11008: Too many config files nested

You can only nest up to 16 config files.

Fatal error 11009: Unable to open file 〈arg. 1〉

The option file cannot be found.

Reading further options from 〈arg. 1〉

Displayed when you have notes turned on, and the compiler switches to another options file.

Warning 11011: Target is already set to: 〈arg. 1〉

Displayed if more than one -T option is specified.

Warning 11012: Shared libs not supported on DOS platform, reverting to static

If you specify -CD for the dos platform, this message is displayed. The compiler supports only static libraries under dos.

Fatal error 11013: In options file 〈arg. 1〉 at line 〈arg. 2〉 too many #IF(N)DEFs encountered

The #IF(N)DEF statements in the options file are not balanced with the #ENDIF statements.

Fatal error 11014: In options file 〈arg. 1〉 at line 〈arg. 2〉 unexpected #ENDIFs encountered

The #IF(N)DEF statements in the options file are not balanced with the #ENDIF statements.

Fatal error 11015: Open conditional at the end of the options file

The #IF(N)DEF statements in the options file are not balanced with the #ENDIF statements.

Warning 11016: Debug information generation is not supported by this executable

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.

Hint 11017: Try recompiling with -dGDB

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.

Warning 11018: You are using the obsolete switch 〈arg. 1〉

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.

Warning 11019: You are using the obsolete switch 〈arg. 1〉, please use 〈arg. 2〉

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.

Note 11020: Switching assembler to default source writing assembler

This notifies you that the assembler has been changed because you used the -a switch, which cannot be used with a binary assembler writer.

Warning 11021: Assembler output selected ”〈arg. 1〉” is not compatible with ”〈arg. 2〉”

Warning 11022: ”〈arg. 1〉” assembler use forced

The assembler output selected cannot generate object files with the correct format. Therefore, the default assembler for this target is used instead.

Reading options from file 〈arg. 1〉

Options are also read from this file.

Reading options from environment 〈arg. 1〉

Options are also read from this environment string.

Handling option ”〈arg. 1〉”

Debug info that an option is found and will be handled.

*** press enter ***

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.

Hint 11030: Start of reading config file 〈arg. 1〉

Start of configuration file parsing.

Hint 11031: End of reading config file 〈arg. 1〉

End of configuration file parsing.

Interpreting option ”〈arg. 1〉”

The compiler is interpreting an option

Interpreting firstpass option ”〈arg. 1〉”

The compiler is interpreting an option for the first time.

Interpreting file option ”〈arg. 1〉”

The compiler is interpreting an option which it read from the configuration file.

Reading config file ”〈arg. 1〉”

The compiler is starting to read the configuration file.

Found source file name ”〈arg. 1〉”

Additional information about options. Displayed when you have the debug option turned on.

Error 11039: Unknown codepage ”〈arg. 1〉”

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.

Fatal error 11040: Config file 〈arg. 1〉 is a directory

Directories cannot be used as configuration files.

Warning 11041: Assembler output selected ”〈arg. 1〉” cannot generate debug info, debugging disabled

The selected assembler output cannot generate debugging information, debugging option is therefore disabled.

Warning 11042: Use of ppc386.cfg is deprecated, please use fpc.cfg instead

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.

Fatal error 11043: In options file 〈arg. 1〉 at line 〈arg. 2〉 #ELSE directive without #IF(N)DEF found

An #ELSE statement was found in the options file without a matching #IF(N)DEF statement.

Fatal error 11044: Option ”〈arg. 1〉” is not, or not yet, supported on the current target platform

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.

Fatal error 11045: The feature ”〈arg. 1〉” is not, or not yet, supported on the 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.

Note 11046: DWARF debug information cannot be used with smart linking on this target, switching to static linking

Smart linking is currently incompatible with DWARF debug information on most platforms, so smart linking is disabled in such cases.

Warning 11047: Option ”〈arg. 1〉” is ignored for the current target platform.

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.

Warning 11048: Disabling external debug information because it is unsupported for the selected target/debug format combination.

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.

Note 11049: DWARF debug information cannot be used with smart linking with external assembler, disabling static library creation.

Smart linking is currently incompatble with DWARF debug information on most platforms, so smart linking is disabled in such cases.

Error 11050: Invalid value for MACOSX_DEPLOYMENT_TARGET environment variable: 〈arg. 1〉

Error 11051: Invalid value for IPHONEOS_DEPLOYMENT_TARGET environment variable: 〈arg. 1〉

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.

Error 11052: You must use one of the VFP FPU types when using the EABIHF ABI target

The EABIHF (VFP hardfloat) ABI target can only be used with VFP FPUs.

Warning 11053: The selected debug format is not supported on the current target, not changing the current setting

Not all targets support all debug formats (in particular, Stabs is not supported on 64 bit targets).

Error 11054: Argument to ”〈arg. 1〉” is missing

Displayed when parameter must be followed by an argument.

Error 11055: Malformed parameter: 〈arg. 1〉

Given argument is not valid for parameter.

Warning 11056: Smart linking requires external linker

Error 11057: Creating .COM files is not supported in the current memory model. Only the tiny memory model supports making .COM files.

Do not enable experimental -gc option if -Ur option is given.

Warning 11058: Experimental CheckPointer option not enabled because it is incomptatible with -Ur option.

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.

Error 11059: Unsupported target architecture -P〈arg. 1〉, invoke the ”fpc” compiler driver instead.

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

Error 11060: Feature switches are only supported while compiling the system unit.

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.

Note 11061: The selected debug format is not supported by the internal linker, switching to external linking

Error 11062: You can not use both options (〈arg. 1〉) (〈arg. 2〉) at same time.

Fatal error 11063: The selected FPU type ”〈arg. 1〉” is not supported by the selected instruction set ”〈arg. 2〉”

Not all instruction sets support all FPU types. For example on ARM, Thumb(-1) supports no FPU/VFP instruction set

Error 11064: Only one WebAssembly exception support mode can be specified.

Only one WebAssembly exception support mode (NOEXCEPTIONS, JSEXCEPTIONS, BFEXCEPTIONS or NATIVEEXCEPTIONS) can be specified.

Warning 11065: Subtarget is already set to: 〈arg. 1〉

Displayed if more than one -t option is specified.

Error 11066: Subtarget 〈arg. 1〉 specified but no corresponding config file 〈arg. 2〉 found.

Displayed if more than one -t option is specified.

Note 11067: Ignoring compiler executable suffix 〈arg. 1〉.

Displayed if more than one -t option is specified.