eld Manual
Table Of Contents
- eld Manual
- Legal Notices
- Contents
- What’s New in This Manual
- Manual Information
- New and Changed Information
- About This Manual
- Notation Conventions
- 1 Introduction to eld
- 2 eld Input and Output
- 3 Binding of References
- Overview
- Presetting Loadfiles
- To Preset or Not to Preset, and Creation of the LIC
- Handling Unresolved References
- Using User Libraries
- Creating Import Libraries
- Ignoring Optional Libraries
- Merging Symbols Found in Input Linkfiles
- Accepting Multiply-Defined Symbols
- Using the -cross_dll_cleanup option
- Specifying Which Symbols to Export, and Creating the Export Digest
- Public Libraries and DLLs
- The Public Library Registry
- 4 Other eld Processing
- Adjusting Loadfiles: The -alf Option
- Additional rules about -alf
- The -set and -change Options
- eld Functionality for 64-Bit
- Checking the C++ Language Dialect
- Renaming Symbols
- Creating Linker-Defined Symbols
- Updating Or Stripping DWARF Symbol Table Information
- Modifying the Data Sections that Contain Stack Unwinding Information
- Creating the MCB
- Processing of Floating Point Versions and Data Models
- Specification of the Main Entry Point
- Specifying Runtime Search Path Information for DLLs
- Merging Source RTDUs
- 5 Summary of Linker Options
- 6 Output Listings and Error Handling
- A TNS/E Native Object Files
- Glossary
- Index

Output Listings and Error Handling
eld Manual—527255-009
6-86
Error Messages
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. This indicates some problem with the procedure for building the NSK
operating system, which is beyond the scope of this manual.
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”. eld did find a
file by these methods, but the file turned out not to have the proper structure for a
zimpimp file. This particular message comes out when the file did have the structure of
a DLL, but did not have the proper “DLL name” within it, to indicate that it was the
zimpimp file.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. There is something wrong with your installation. The message told the
name of the file that eld thought should be the zimpimp file, but wasn’t. Perhaps that
will help you figure out what is wrong. A proper zimpimp file should be built as part of
the process of creating the operating system, which is beyond the scope of this
manual.
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”. eld did find a
file by these methods, but the file turned out not to have the proper structure for a
zimpimp file. This particular message comes out when the file was not a DLL, which is
what the zimpimp file looks like, but rather was a linkfile, such as an object file created
by a compilation.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. There is something wrong with your installation. The message told the
name of the file that eld thought should be the zimpimp file, but wasn’t. Perhaps that
will help you figure out what is wrong. A proper zimpimp file should be built as part of
the process of creating the operating system, which is beyond the scope of this
manual.
1537 The file named <filename>, which should be a zimpimp
file, is not a zimpimp file.
1538 <filename> is a linkfile but a zimpimp file was
expected.
1539 Option -public_registry specified multiple times with
different filenames <filename> and <filename>.










