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-64
Error Messages
Cause. You used the -instance_data option, which affects the layout of the
program or DLL that you are creating, and you also used the -r option, to tell eld to
build another object file that can be used as linker input, rather than a program or DLL.
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. If your intention is to create a program or DLL, then don’t specify the -r
option. If your intention is to use the -r option to tell eld to make another object file
that can be used as eld input, then don’t specify the -instance_data option.
Cause. While reading the private DLL registry that was specified for this link in the -
check_registry or -update_registry option, eld ran off the end of the file when it was
expecting that the next thing in the file would be a number. Presumably, the format of
the file is bad because it was incorrectly edited by hand.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Fix the format of the file, as explained elsewhere in this manual.
Cause. You gave the -rename option, which requires two symbol name parameters.
However, the next two things on the command line were not symbol name parameters.
Either there were no symbol name parameters, or there was only one, and then it was
either the end of the command line or the next token on the command line started with
a hyphen, indicating another option rather than another parameter to this one.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you want to specify this option, fix the syntax.
Cause. While reading the private DLL registry that was specified for this link in the -
check_registry or -update_registry option, at the line indicated in the message, eld
expected to see a number, but the next thing in the file was not a number with the
correct format. Presumably, the format of the file is bad because it was incorrectly
edited by hand.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Fix the format of the file, as explained elsewhere in this manual.
1359 DLL registry line <number>: encountered end of file when
expecting a number.
1360 Two symbol names are required for the -rename option.
1361 DLL registry line <number>: number expected but not
found.










