
Output Listings and Error Handling
eld Manual—527255-009
6-93
Error Messages
parses the contents of the file into “statements”, which in turn can have “attributes”, and
a “dll” statement always contains a “file” attribute, which tells the DLLs name. This
particular message comes out when
eld
saw two different “dll” statements with the
same name.
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.
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”. Or, you can
simply put the name of the zimpimp file directly on the
eld
command line. However,
none of these methods specified a zimpimp file to
eld
.
Effect.
Warning.
eld
will continue to produce an output file, but it will not be able to
fix up references to system library.
Recovery.
It is not necessary to have references fixed up at link time. However,
normally,
eld
should find a zimpimp file. So, this may indicate that there is something
wrong with your installation. A proper zimpimp file should be built as part of the
process of creating the operating system, and then installed in the proper location for
eld
to find it. The process of creating the operating system is beyond the scope of
this manual.
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, none of these methods specified
a public DLL registry file to
eld
.
Effect.
Warning.
eld
will continue to produce an output file, but it will not be able to
fix up references to standard DLLs.
1551 This link is not using any zimpimp file.
1552 This link is not using any public DLL registry file.
Summary of Contents for eld
Page 4: ......
Page 8: ...Contents eld Manual 527255 009 iv ...
Page 12: ...What s New in This Manual eld Manual 527255 009 viii Changes to the 527255 005 Manual ...
Page 34: ...Introduction to eld eld Manual 527255 009 1 14 Example of Use ...
Page 54: ...eld Input and Output eld Manual 527255 009 2 20 Using Archives ...
Page 98: ...Other eld Processing eld Manual 527255 009 4 20 Merging Source RTDUs ...
Page 242: ...Output Listings and Error Handling eld Manual 527255 009 6 132 Glossary of Errors ...