eld Manual

Output Listings and Error Handling
eld Manual—527255-009
6-92
Error Messages
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, it
is your responsibility to provide eld with a correct public DLL registry file, and it is
beyond the scope of this manual to describe how this file should be created. 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 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. 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
a “dll” statement should always contain a “file” attribute, but this particular message
comes out when eld saw a “dll” statement that did not contain a “file” attribute. The
message tells the line number at which this statement began in the file.
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, it
is your responsibility to provide eld with a correct public DLL registry file, and it is
beyond the scope of this manual to describe how this file should be created. 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 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. 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
1549 No file attribute in the 'dll' statement that started at
line <number> in <filename>.
1550 More than one 'dll' statement with name <string> in
<filename>.