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-63
Error Messages
option names beginning with an “o” are “-obey” and “-optional_lib”, and they must be
spelled exactly that way, except for case.
Cause. You specified the -make_import_lib option, which means that you are either
making an import library to represent a single DLL, or that you are making the zimpimp
file that represents all the implicit DLLs that constitute system library. You also
specified either the -unres_symbols, -error_unresolved, or -warning_unresolved option,
and these are options that are allowed when you are creating the zimpimp file, but not
when creating other kinds of import libraries. On the other hand, you also put the
name of a DLL on the command line, and this DLL isn’t an implicit DLL, but only
implicit DLLs are allowed when you are creating the zimpimp file. So, this set of
conditions is inconsistent.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If your intention is to create a zimpimp file, then the other filenames on the
command line should be implicit DLLs. If you are trying to create an import library to
represent a single (ordinary) DLL, then don’t use the option that was mentioned in the
message. If you are not trying to create an import library, don’t specify the -
make_import_lib option.
Cause. You have specified the -instance_data data1constant option, which
means that you want eld to consider it an error if the program or DLL that you are
building contains any writeable data. And, indeed, the input file mentioned in the
message contains writeable data.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Assuming you really don’t want to have any writeable data, you need to
examine your input files to determine why they contain variable data, modify them, and
recompile them, to fix that.
1356 Options to specify how unresolved references should be
handled would be allowed if you were making a zimpimp file,
but because the DLL on the command line is not an implicit
DLL, you are instead making an ordinary import library, in
which case such options are not allowed.
1357 <filename>: <message about why this input file contains
something that would lead to the existence of variable data
in the output file>, which is not allowed when -instance_data
data1constant is specified.
1358 The -instance_data option cannot be specified with the
-r option.










