C.1 General compiler messages

This section gives the compiler messages which are not fatal, but which display useful information. The number of such messages can be controlled with the various verbosity level -v switches.

Compiler: 〈arg. 1⟩

When the -vt switch is used, this line tells you what compiler is used.

Compiler OS: 〈arg. 1⟩

When the -vd switch is used, this line tells you what the source operating system is.

Info 1002: Target OS: 〈arg. 1⟩

When the -vd switch is used, this line tells you what the target operating system is.

Using executable path: 〈arg. 1⟩

When the -vt switch is used, this line tells you where the compiler looks for its binaries.

Using unit path: 〈arg. 1⟩

When the -vt switch is used, this line tells you where the compiler looks for compiled units. You can set this path with the -Fu option.

Using include path: 〈arg. 1⟩

When the -vt switch is used, this line tells you where the compiler looks for its include files (files used in {$I xxx} statements). You can set this path with the -Fi option.

Using library path: 〈arg. 1⟩

When the -vt switch is used, this line tells you where the compiler looks for the libraries. You can set this path with the -Fl option.

Using object path: 〈arg. 1⟩

When the -vt switch is used, this line tells you where the compiler looks for object files you link in (files used in {$L xxx} statements). You can set this path with the -Fo option.

Info 1008: 〈arg. 1⟩ lines compiled, 〈arg. 2⟩ sec〈arg. 3⟩

When the -vi switch is used, the compiler reports the number of lines compiled, and the time it took to compile them (real time, not program time).

Fatal error 1009: No memory left

The compiler doesn’t have enough memory to compile your program. There are several remedies for this:

• If you’re using the build option of the compiler, try compiling the different units manually.

• If you’re compiling a huge program, split it up into units, and compile these separately.

• If the previous two don’t work, recompile the compiler with a bigger heap. (You can use the -Ch option for this, -Ch (see page 114).)

Info 1010: Writing Resource String Table file: 〈arg. 1⟩

This message is shown when the compiler writes the Resource String Table file containing all the resource strings for a program.

Error 1011: Writing Resource String Table file: 〈arg. 1⟩

This message is shown when the compiler encounters an error when writing the Resource String Table file.

Info 1012: Fatal:

Prefix for Fatal Errors.

Info 1013: Error:

Prefix for Errors.

Info 1014: Warning:

Prefix for Warnings.

Info 1015: Note:

Prefix for Notes.

Info 1016: Hint:

Prefix for Hints.

Error 1017: Path ”〈arg. 1⟩” does not exist

The specified path does not exist.

Fatal error 1018: Compilation aborted

Compilation was aborted.

bytes code

The size of the generated executable code, in bytes.

bytes data

The size of the generated program data, in bytes.

Info 1021: 〈arg. 1⟩ warning(s) issued

Total number of warnings issued during compilation.

Info 1022: 〈arg. 1⟩ hint(s) issued

Total number of hints issued during compilation.

Info 1023: 〈arg. 1⟩ note(s) issued

Total number of notes issued during compilation.

Fatal error 1024: I/O error: 〈arg. 1⟩

During compilation an I/O error happened which allows no further compilation.

Fatal error 1025: Operating system error: 〈arg. 1⟩

During compilation an operating system error happened which allows no further compilation.

Error 1026: Compilation raised exception internally

Compilation was aborted, due to an exception generation.

Using unit scope: 〈arg. 1⟩

When the -vt switch is used, this line tells you what unit scopes (namespaces) the compiler is using when looking up units. You can add a unit scope with the -FN option.

Info 1028: Reduced file search: Not searching for uppercased or 8.3 unit filenames.

When the -Ft switch is used, this line informs you that the compiler will not look for uppercased filenames or 8.3 conforming filenames.

Fatal error 1029: Compiler stopped

Compilation was aborted.

〈arg. 1⟩: Using local unit path: 〈arg. 2⟩

When the -vt switch is used, this line tells you where the compiler looks for compiled units. You can set this path with the {$UNITPATH xxx} directive.

〈arg. 1⟩: Using local include path: 〈arg. 2⟩

When the -vt switch is used, this line tells you where the compiler looks for its include files (files used in {$I xxx} statements). You can set this path with the {$INCLUDEPATH xxx} directive.

〈arg. 1⟩: Using local library path: 〈arg. 2⟩

When the -vt switch is used, this line tells you where the compiler looks for the libraries. You can set this path with the {$LIBRARYPATH xxx} directive.

〈arg. 1⟩: Using local object path: 〈arg. 2⟩

When the -vt switch is used, this line tells you where the compiler looks for object files you link in (files used in {$L xxx} statements). You can set this path with the {$OBJECTPATH xxx} directive.