This section lists all messages that can occur when the compiler is loading a package from disk into
memory, saving a package from memory to disk or when parsing packages in general. Many of these
messages are informational messages.
-
Fatal: Can’t find package arg1
-
You tried to use a package of which the PCP file isn’t found by the compiler. Check
your configuration file for the package paths.
-
PCP file for package arg1 found
-
The PCP file for the specified package was found.
-
Error: Duplicate package arg1
-
The package was already specified as required package and may not be specified a
second time.
-
Error: Unit arg1 can not be part of a package
-
The unit can not be part of a package because the DenyPackageUnit directive is enabled
for the unit.
-
Note: Unit arg1 is implicitely imported into package arg2
-
The unit was not specified as part of the contains section and is also not included
in one of the required packages. Add the unit to the contains section to increase
compatibility with other packages.
-
Fatal: Failed to create PCP file arg2 for package arg1
-
The PCP file for the package could not be created.
-
Fatal: Failed to read PCP file for package arg1
-
The PCP file for the package could not be read.
-
PCP loading arg1
-
When the -vt switch is used, the compiler tells you what packages it loads.
-
PCP Name: arg1
-
When you use the -vu flag, the package name is shown.
-
PCP Flags: arg1
-
When you use the -vu flag, the package flags are shown.
-
PCP Crc: arg1
-
When you use the -vu flag, the package CRC check is shown.
-
PCP Time: arg1
-
When you use the -vu flag, the time the package was compiled is shown.
-
PCP File too short
-
The PCP file is too short, not all declarations are present.
-
PCP Invalid Header (no PCP at the begin)
-
A package file contains as the first three bytes the ASCII codes of the characters PCP.
-
PCP Invalid Version arg1
-
This package file was compiled with a different version of the compiler, and cannot be
read.
-
PCP is compiled for another processor
-
This package file was compiled for a different processor type, and cannot be read.
-
PCP is compiled for another target
-
This package file was compiled for a different target, and cannot be read.
-
Writing arg1
-
When you specify the -vu switch, the compiler will tell you where it writes the package
file.
-
Fatal: Can’t Write PCP-File
-
An error occurred when writing the package file.
-
Fatal: Error reading PCP-File
-
This means that the package file was corrupted, and contains invalid information.
Recompilation will be necessary.
-
Fatal: unexpected end of PCP-File
-
Unexpected end of file. This may mean that the PCP file is corrupted.
-
Fatal: Invalid PCP-File entry: arg1
-
The unit the compiler is trying to read is corrupted, or generated with a newer version
of the compiler.
-
Trying to use a unit which was compiled with a different FPU mode
-
Trying to compile code while using units which were not compiled with the same
floating point format mode. Either all code should be compiled with FPU emulation
on, or with FPU emulation off.
-
Packagesearch: arg1
-
When you use the -vt option, the compiler tells you where it tries to find package files.
-
Required package arg1
-
When you specify the -vu switch, the compiler will tell you which packages a package
requires.
-
Contained unit arg1
-
When you specify the -vu switch, the compiler will tell you which units a package
contains.
-
Error: Unit arg1 is already contained in package arg2
-
A unit specified in a contains sections must not be part of a required package. Note
that a unit might have become part of another package by indirectly including it.
-
Warning: Unit arg1 is imported from indirectly required package arg2
-
If a unit from a package that is not part of the requires section is used then the
package should require this unit directly to avoid confusion.
-
PPL filename arg1
-
The name of the binary package library that is stored in the PCP.