eld Manual

Output Listings and Error Handling
eld Manual—527255-009
6-61
Error Messages
Cause. You gave the -check_registry option, to tell eld the name of an existing
private DLL registry for eld to use during the link, but no such file exists.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Check that you spelled the name of the private DLL registry correctly.
Cause. The program or DLL that you are building contains writeable data and you
have not specified the -instance_data option with an appropriate parameter value
to cause eld to separate the writeable data from other data so that NSK can give them
different types of protection. Also, you have resident code in your program or DLL, and
you have not specified the -data_resident option, to tell NSK that the data for this
program needs to be resident. That combination of conditions is considered an error.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Yes, this is tricky. Most users who have both writeable data and resident
code should specify the -instance_data data2 option to make things work. It is
beyond the scope of this manual to explain when you might instead prefer to specify -
instance_data data2protected or -instance_data data2hidden, which is
the other possible choice for the -instance_data option that also makes eld create
two data segments. And, none of this is the right thing to do for certain special
programs that are called “proto-processes” or “sysgen’ed processes”. It is similarly
beyond the scope of this manual to explain what these things are, but if you are
creating a proto-process then you should know that you are doing that. In that case,
do not specify the -instance_data option, but rather the -data_resident option.
Cause. You have specified the -make_implicit_lib option, to make one of the implicit
DLLs that constitute system library. When an implicit DLL is created, eld does not use
the zimpimp file, which is the import library that represents the entire set of implicit
DLLs after they have all been created. So, when you are making an implicit DLL, eld
doesn’t try to find the zimpimp file on its own. However, one of the files that eld found,
when it was looking for normal DLLs, turned out to be a zimpimp file. That’s the error.
Effect. Fatal error (eld immediately stops without creating an output file).
1348 DLL registry <filename> not found.
1349 You are building a program or a DLL, and you have both
resident code and writeable data. To build such a file you
are required to specify the -instance_data data2 option.
Except, if you are building a 'proto-process' (also known as
a 'sysgen'ed process'), then instead you should specify the
-data_resident option.
1350 A zimpimp file (<filename>) is not allowed when you are
building an implicit DLL.