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-37
Error Messages
Cause. You specified the -make_import_lib option, in order to create the zimpimp file
that represents the multiple implicit DLLs that constitute system library, and you also
specified those implicit DLLs on the command line. One of the checks that eld
performs on these implicit DLLs is that they don’t have unresolved references, which
would have to be true if that implicit DLL was correctly fixed up at the time it was
linked. But, the implicit DLL mentioned in the message had unresolved references.
Effect. Fatal error (The linker cannot do what was requested of it and the linker
immediately stops).
Recovery. This indicates some problem with the procedure for building and installing
the NSK operating system, which is beyond the scope of this document.
Cause. You specified the -make_import_lib option, in order to create the zimpimp file
that represents the multiple implicit DLLs that constitute system library, and you also
specified those implicit DLLs on the command line. One of the checks that eld
performs on these implicit DLLs is that they don’t have unresolved references, which
would have to be true if that implicit DLL was correctly fixed up at the time it was
linked. But, the implicit DLL mentioned in the message had unresolved references. It
is only a warning message, not an error message, because the -unres_symbols warn
option was also specified.
Effect. Warning (eld produces an output file, but it might not be what you intended).
Recovery. This issue involves the procedure for building and installing the NSK
operating system, which is beyond the scope of this document.
Cause. You specified the -show_multiple_def option, to tell eld to put information into
the listing about symbols that were defined more than once. This message reports the
first two definitions that eld saw for the symbol named in the message.
Effect. Information (This is not indicative of a problem).
Recovery. No action required.
Cause. You specified the -show_multiple_def option, to tell eld to put information into
the listing about symbols that were defined more than once. There was an instance of
message number 1227 earlier, which reported the first two definitions that eld saw for
1215 The implicit DLL <filename> has unresolved references.
1227 Multiple definition of <symbol name>: first definition
found in <filename>, second definition found in <filename>.
1228 Multiple definition of <symbol name>: third or later
definition found in <filename>.










