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-100
Error Messages
in the input object files, and are visible outside their own compilations, can be
exported, and such a symbol of this name did not exist.
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. Check that you spelled the name of the symbol correctly. In pTAL or
Cobol, for example, it must be given in upper case. In C or C++, symbol names are
case sensitive. Is the symbol defined (not just an external reference), and visible
outside its compilation? The rules for which symbols are defined by a compilation, and
visible outside that compilation, depend on the source language, and are beyond the
scope of this manual.
Cause. You gave the -exported_symbol option (or its synonym, the -export option) to
say that a certain symbol should be exported. In fact, eld has seen such a symbol,
perhaps in a DLL, or perhaps as an external reference from the program or DLL being
built. However, only symbols that are defined in the input object files can be exported,
and such a symbol of this name did not exist.
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. The symbol must be defined (not just an external reference). The rules for
which symbols are defined by a compilation depend on the source language, and are
beyond the scope of this manual.
Cause. You gave the -hidden_symbol option (or its synonym, the -export_not option)
to say that a certain symbol should not be exported. However, only symbols that are
defined in the input object files, and are visible outside their own compilations, can be
exported, and such a symbol of this name did not exist.
Effect. Warning (eld produces an output file, but it might not be what you intended).
Recovery. Saying that a symbol should not be exported, and no such symbol existed
in the first place, is not necessarily an error, but you probably want to make your link
clean. If no such symbol is present, don’t give this option. If you think that there
should be such a symbol, check that you spelled the name of the symbol correctly. In
pTAL or Cobol, for example, it must be given in upper case. In C or C++, symbol
names are case sensitive. Is the symbol defined (not just an external reference), and
visible outside its compilation? The rules for which symbols are defined by a
compilation, and visible outside that compilation, depend on the source language, and
are beyond the scope of this manual.
1570 The -exported_symbol <symbol name> is not defined in any
of the input linkfiles.
1571 The -hidden_symbol <symbol name> is not present.










