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-9
Error Messages
that need to be initialized with the addresses of procedures, in the file you are building
or some other DLL, whose addresses can’t be represented in 32 bits.
Effect. Error (The linker cannot do what was requested of it and will eventually stop,
but may continue for the purpose of detecting additional errors before stopping).
Recovery. Did you need to use the -t and -d options? There usually is no reason to
use these options when building a program, and there usually is no reason to use the -
d
option at all. But, if you want to assign addresses to this program or DLL that don’t fit
into 32 bits, or make references to some other DLL that has a range of addresses that
doesn’t fit into 32 bits, then change your source code so that it doesn’t try to use 32-bit
procedure pointers in those cases.
Cause. You are building a program or DLL that has the HIGHPIN attribute set ON,
which is the default, but during the link one or more of the DLLs that eld looked at had
the HIGHPIN attribute set OFF.
Effect. Warning (eld produces an output file, but it might not be what you intended).
Recovery. This is only considered a warning by eld because what matters is which
DLLs you will be using at runtime. Determine which of your programs and DLLs
should have HIGHPIN ON, and which should have it OFF. The rule is that a program
or DLL with HIGHPIN ON cannot be a client of a DLL with HIGHPIN OFF. Your
program must satisfy this rule or NSK will not allow it to run. If you also satisfy this rule
at link time, your link won’t produce this warning message.
Cause. eld prints out informational messages about some of the files that it used and
what types of files they were. In this case, it is telling you about a complete import
library.
Effect. Information (This is not indicative of a problem).
Recovery. No action required.
Cause. eld prints out informational messages about some of the files that it used and
what types of files they were. In this case, it is telling you about an incomplete import
library.
Effect. Information (This is not indicative of a problem).
Recovery. No action required.
1014 The output program or DLL has highpin on, although DLL
<filename> has highpin off.
1017 Using complete import library <filename>.
1018 Using incomplete import library <filename>.