HP eld Manual page 204

Output Listings and Error Handling
Recovery. It is not necessary to have references fixed up at link time. However,
normally, eld should find the public DLL registry file. So, this may indicate that there is
something wrong with your installation. The process of creating and installing the
public DLL registry file is beyond the scope of this manual.
1553 <filename> is an archive, but eld was expecting a
zimpimp file.
Cause. The zimpimp file is a file that tells eld about the symbols in system library.
eld has various methods of locating this file. For example, if you are running eld on
TNS/E then the operating system tells eld where the file is. In other cases, eld looks
for it in an appropriate place, expecting it to have the name "zimpimp". eld did find a
file by these methods, but the file turned out not to have the proper structure for a
zimpimp file. This particular message comes out when the file was not a DLL, which is
what the zimpimp file looks like, but rather was a archive, as would be created by the
"ar" tool.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. There is something wrong with your installation. The message told the
name of the file that eld thought should be the zimpimp file, but wasn't. Perhaps that
will help you figure out what is wrong. A proper zimpimp file should be built as part of
the process of creating the operating system, which is beyond the scope of this
manual.
1554 Can't open public DLL file named <filename>. Such a file
should be in the same place as the zreg file.
Cause. eld is searching for a DLL, and you are using eld on Guardian. eld found
the name mentioned in the message in the public DLL registry file, meaning that this
DLL is one of the standard DLLs and is supposed to exist in a certain location.
Specifically, it is required that there be a file named "zxxxdll" in the same location
(Guardian subvolume, OSS directory, or PC folder) as the public DLL registry file. But,
either such a file does not exist, or you don't have permission to read it.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. There are various ways that eld may find the public DLL registry file. For
example, if you are running eld on TNS/E then the operating system tells eld where
the file is. In other cases, eld looks for it in an appropriate place, expecting it to have
the name "zreg". The first place eld looks is its own location (Guardian subvolume,
OSS directory, or PC folder), and if there is no "zreg" file there then it will also look in a
sibling directory or folder whose name ends "lib". Or, you can override these methods
by explicitly telling eld where it is with the -public_registry option. The file mentioned
in the message was supposed to exist in the same place as that public DLL registry
file, but wasn't. If you gave the -public_registry option, then you are responsible for
setting up all the files correctly. Otherwise, there is something wrong with your
eld Manual—527255-009
6-94
Error Messages