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-44
Error Messages
Recovery. Check that you have issued a MAP DEFINE prior to running eld, where
this MAP DEFINE equated that string that began with an equal sign to a filename.
Also check that DEFMODE is ON.
Cause. You specified a string that began with an equal sign on the command line, and
you are running the Guardian version of eld. eld treated the string as a “Guardian
DEFINE”, and succeeded in expanding it to a filename. The message shows you how
it was expanded.
Effect. Information (This is not indicative of a problem).
Recovery. No action required.
Cause. You specified the option named in the message, and this option requires a
keyword parameter, but the option itself was the last thing on the command line, with
no keyword parameter after it.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you want to specify this option, fix the syntax.
Cause. You specified the option named in the message, and this option requires a
keyword parameter, but the next token on the command line began with a hyphen,
indicating another option, not the parameter for 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. You specified the option named in the message, and this option requires a
number as a parameter, but the option itself was the last thing on the command line,
with no parameter after it. Or, it is also possible to get this message if the next thing on
the command line was a string such as “0x”, which is the prefix signifying the start of a
hexadecimal number, but immediately after the “0x” there was just a space, or the end
of the command line.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you want to specify this option, fix the syntax.
1285 The MAP DEFINE <string> was expanded to <string>.
1286 Parameter required for <option name>.
1287 Keyword parameter required for <option name>.
1288 Number required for <option name>.










