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-114
Error Messages
specified for the process subtype. The new file that eld creates will have the process
subtype that you specified this time, not the value that was in the previous file.
Effect. Warning (eld produces an output file, but it might not be what you intended).
Recovery. Assuming you gave the file the wrong process subtype before, or had
some other reason to change it now, no action is required.
Cause. You gave a -r option, and exactly one input object file, to tell eld to create
another object file that could be used as eld input again, and you also gave the -set
floattype option, to tell eld which floating point type to indicate in the output
object file, and it was different from what the input file contained.
Effect. Information (This is not indicative of a problem).
Recovery. Assuming you gave the file the wrong floating point type before, or had
some other reason to change it now, no action is required.
Cause. You used the -set user_buffers option, which affects how a program
performs I/O, 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.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If your intention is to create a program, then don’t specify the -r option. If
your intention is to use the -r option to create a new object file that can be used as
eld input, then don’t specify the -set user_buffers 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 to see the name of a DLL after the -range keyword.
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.
1612 The floating point type of the input file, which was
<string>, has been changed to <string>.
1613 The -set user_buffers option is not allowed with the -r
option.
1614 DLL registry, line <number>: end of file in the middle
of a -range command.










