Table of Contents
Advertisement
Output Listings and Error Handling
two statements or between two attributes. The message tells the line number at which
this occurred in the file.
Effect. Warning. It is possible that the format of the official public DLL registry file
changed, and that is why eld cannot read it, but still eld tries to continue with the link.
Because eld could not read the public DLL registry file, however, that means that eld
will not be able to automatically find any of the standard DLLs.
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
1542 Statement starting at line <number> of the public DLL
registry file <filename> went off the end of file.
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", and there are many statements that eld
simply ignores, and this particular message comes out when eld was trying to skip
over a statement by searching for the final semicolon but ran off the end of the file
instead. 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.
eld Manual—527255-009
6-88
Error Messages
Advertisement
Table of Contents
