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-84
Error Messages
Cause. eld normally looks for a “zimpimp” file, based on which it gets information
about the symbols in system library, and this message is just telling you where eld
found this file.
Effect. Information (This is not indicative of a problem).
Recovery. No action required.
Cause. Procedures may be given the CALLABLE attribute, which means that code
goes into privileged mode when such procedures are called. Obviously, this attribute is
only used by a limited number of people. There is also an attribute called
KERNEL_CALLABLE, which is even more restricted, only occuring in the millicode
DLL that is part of system library. A single DLL is not allowed to contain a mixture of
procedures with both of these attributes, but both of these attributes were used
somewhere among the input files that you gave to eld.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you are one of the persons who should be using these attributes in the
first place, and having this problem, then it is a problem with building the NSK
operating system that is beyond the scope of this manual.
Cause. You specified the -change incomplete option, to mark an existing import
library as an incomplete import library. However, the file name that you specified for
the -change option is in fact a zimpimp file, the special import library that represents
the procedures in system library, and you are not allowed to mark that file incomplete.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If your intention was to mark some other import library as incomplete,
specify its name correctly. You cannot mark the zimpimp file incomplete.
Cause. The C++ compiler marks some symbols as “globalized” symbols, because the
fixups to such symbols need to follow special rules at runtime. You have globalized
symbols in the files that you are linking together, as indicated in the message. You
1530 Using the zimpimp file <filename>.
1532 User_callable and kernel_callable procedures are both
present.
1533 The 'incomplete' attribute is not allowed for implicit
DLL's.
1534 Globalized symbols (first one: <symbol name>) are not
allowed in an implicit DLL.