eld Manual

Output Listings and Error Handling
eld Manual—527255-009
6-87
Error Messages
Cause. The -public_registry option specifies the name of a public DLL registry file,
which eld uses to look up information about the operating system and other standard
DLLs. You gave this option twice on the command line, and you specified different
names each time, which is an error. Note that case is significant for this check.
Effect. Fatal error (eld immediately stops without creating an output file).
Cause. Are you sure you want to specify the -public_registry option at all? There
usually is no need to give this option, because eld should be able to find the official
version automatically. If you specify this option, you can do it more that once, but only
if you specify the same filename each time.
Cause. eld uses the public DLL registry file to look up information about the operating
system and other standard DLLs. There are various ways that eld may find 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 “zreg”. Or, you can override these methods by explicitly telling eld
where it is with the -public_registry option. However eld was told where the public
DLL registry file was, either a file of that name didn’t exist, or you don’t have
permission to read it.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you specified the -public_registry option, are you sure you need to do
that? There usually is no need to give this option, because eld should be able to find
the official version of the public DLL registry automatically. If you specify this option,
check that you spelled the name correctly, and that you do have permission to read it.
If eld could not find it on its own, and you didn’t specify the -public_registry option,
then there is something wrong with your installation. The message told the name of
the file that eld thought was the public DLL registry file. Perhaps that will help you
figure out what’s wrong.
Cause. eld uses the public DLL registry file to look up information about the operating
system and other standard DLLs. There are various ways that eld m
ay find 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 “zreg”. Or, you can override these methods by explicitly telling eld
where it is with the -public_registry option. eld did find a file by these methods, but
the file turned out not to have the proper structure for a public DLL registry file. eld
parses the contents of the file into “statements”, which in turn can have “attributes”, and
this particular message comes out when eld found unexpected characters between
1540 Cannot open public DLL registry file <filename>.
1541 Unexpected characters <string> found on line <number> of
<filename>.