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-95
Error Messages
installation. The procedure for creating and installing a public DLL registry file is
beyond the scope of this manual.
Cause. You gave a -l option, to tell eld to search for a DLL based on the parameter to
the -l option. Based on that, eld decided that this was one of the standard DLLs,
found it in the standard place, and opened it. The file, however, was not a DLL, but
instead was an archive, as would be created by the “ar” tool.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. There is something wrong with your installation. Files that are not DLLs
have been placed in the location for the standard (“public”) DLLs. The process of
installing the standard DLLs in the standard location is beyond the scope of this
manual.
Cause. You gave a -l option, to tell eld to search for a DLL based on the parameter to
the -l option. Based on that, eld decided that this was one of the standard DLLs,
found it in the standard place, and opened it. The file, however, was not a DLL, but
instead was a linkfile, i.e., an object file created by a compilation or by running eld
with the -r option.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. There is something wrong with your installation. Files that are not DLLs
have been placed in the location for the standard (“public”) DLLs. The process of
installing the standard DLLs in the standard location is beyond the scope of this
manual.
For details on Cause and Recovery, see eld Functionality for 64-Bit
on page 4-12.
Fatal error. eld stops immediately without creating an output file.
Cause. You are building a program, and you are using a user library. A user library is
a DLL, and like any other DLL has a “DLL name” inside it. eld has also opened
another DLL, whose filename is shown in the message, and found that it contained the
1555 <filename> is an archive, but it should have been a
public DLL.
1556 <filename> is a linkfile, but it should have been a
public DLL.
1557 The -set data_model neutral option is not allowed when a
program is being created.
1558 The DLL <filename> contains the same DLL name as the
user library <filename> but is still being used in the link.










