This section lists all messages that can occur when the compiler is loading a unit from disk into
memory. Many of these mesages are informational messages.
-
Unitsearch: arg1
- When you use the -vt, the compiler tells you where it tries to find unit
files.
-
PPU Loading arg1
- When the -vt switch is used, the compiler tells you what units it
loads.
-
PPU Name: arg1
- When you use the -vu flag, the unit name is shown.
-
PPU Flags: arg1
- When you use the -vu flag, the unit flags are shown.
-
PPU Crc: arg1
- When you use the -vu flag, the unit CRC check is shown.
-
PPU Time: arg1
- When you use the -vu flag, the time the unit was compiled is shown.
-
PPU File too short
- The ppufile is too short, not all declarations are present.
-
PPU Invalid Header (no PPU at the begin)
- A unit file contains as the first three
bytes the ascii codes of PPU
-
PPU Invalid Version arg1
- This unit file was compiled with a different version of the
compiler, and cannot be read.
-
PPU is compiled for an other processor
- This unit file was compiled for a different
processor type, and cannot be read
-
PPU is compiled for an other target
- This unit file was compiled for a different target,
and cannot be read
-
PPU Source: arg1
- When you use the -vu flag, the unit CRC check is shown.
-
Writing arg1
- When you specify the -vu switch, the compiler will tell you where it writes
the unit file.
-
Fatal: Can’t Write PPU-File
- An error occurred when writing the unit file.
-
Fatal: Error reading PPU-File
- This means that the unit file was corrupted, and contains
invalid information. Recompilation will be necessary.
-
Fatal: unexpected end of PPU-File
- Unexpected end of file.
-
Fatal: Invalid PPU-File entry: arg1
- The unit the compiler is trying to read is
corrupted, or generated with a newer version of the compiler.
-
Fatal: PPU Dbx count problem
- There is an inconsistency in the debugging information
of the unit.
-
Error: Illegal unit name: arg1
- The name of the unit doesn’t match the file name.
-
Fatal: Too much units
- Free Pascal has a limit of 1024 units in a program. You can change
this behavior by changing the maxunits constant in the files.pas file of the compiler,
and recompiling the compiler.
-
Fatal: Circular unit reference between arg1 and arg2
- Two units are using each
other in the interface part. This is only allowed in the implementation part. At least
one unit must contain the other one in the implementation section.
-
Fatal: Can’t compile unit arg1, no sources available
- A unit was found that needs to
be recompiled, but no sources are available.
-
Warning: Can’t recompile unit arg1, but found modifed include files
- A unit was
found to have modified include files, but some source files were not found, so
recompilation is impossible.
-
Fatal: Can’t find unit arg1
- You tried to use a unit of which the PPU file isn’t found by
the compiler. Check your config files for the unit pathes
-
Warning: Unit arg1 was not found but arg2 exists
-
-
Fatal: Unit arg1 searched but arg2 found
- Dos truncation of 8 letters for unit PPU files
may lead to problems when unit name is longer than 8 letters.
-
Warning: Compiling the system unit requires the -Us switch
- When recompiling
the system unit (it needs special treatment), the -Us must be specified.
-
Fatal: There were arg1 errors compiling module, stopping
- When
the compiler encounters a fatal error or too many errors in a module then it stops with
this message.
-
Load from arg1 (arg2) unit arg3
- When you use the -vu flag, which unit is loaded from
which unit is shown.
-
Recompiling arg1, checksum changed for arg2
-
-
Recompiling arg1, source found only
- When you use the -vu flag, these messages tell
you why the current unit is recompiled.
-
Recompiling unit, static lib is older than ppufile
- When you use the -vu flag, the
compiler warns if the static library of the unit are older than the unit file itself.
-
Recompiling unit, shared lib is older than ppufile
- When you use the -vu flag, the
compiler warns if the shared library of the unit are older than the unit file itself.
-
Recompiling unit, obj and asm are older than ppufile
- When you use the -vu flag,
the compiler warns if the assembler or object file of the unit are older than the unit
file itself.
-
Recompiling unit, obj is older than asm
- When you use the -vu flag, the compiler
warns if the assembler file of the unit is older than the object file of the unit.
-
Parsing interface of arg1
- When you use the -vu flag, the compiler warns that it starts
parsing the interface part of the unit
-
Parsing implementation of arg1
- When you use the -vu flag, the compiler warns that it
starts parsing the implementation part of the unit
-
Second load for unit arg1
- When you use the -vu flag, the compiler warns that it starts
recompiling a unit for the second time. This can happend with interdepend units.
-
PPU Check file arg1 time arg2
- When you use the -vu flag, the compiler show the
filename and date and time of the file which a recompile depends on
-
Hint: Conditional arg1 was not set at startup in last compilation of arg2
- when
recompilation of an unit is required the compiler will check that the same conditionals
are set for the recompiliation. The compiler has found a conditional that currently is
defined, but was not used the last time the unit was compiled.
-
Hint: Conditional arg1 was set at startup in last compilation of arg2
- when
recompilation of an unit is required the compiler will check that the same conditionals
are set for the recompiliation. The compiler has found a conditional that was used the
last time the unit was compiled, but the conditional is currently not defined.
-
Hint: File arg1 is newer than Release PPU file arg2