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-59
Error Messages
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 -s, -x, or -set incomplete option, and these are options that are only
allowed when you are creating some other kind of import library, not the zimpimp file.
On the other hand, the DLLs that you listed on the command line are implicit DLLs, and
that’s only 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 don’t use the option that
was mentioned in the message. If you are trying to create an import library to
represent a single DLL, then that should be the only DLL listed on the command line,
and it should not be an implicit DLL. If you are not trying to create an import library,
don’t specify the -make_import_lib option.
Cause. You have specified the -make_implicit_lib option, which means that you are
building one of the DLLs that constitute system library. These DLLs are not allowed to
contain writeable data. However, the input file mentioned in the message contained
writeable data.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Assuming you really do want to specify the -make_implicit_lib option, you
need to examine your input files to determine why they contain variable data, modify
them, and recompile them, to fix that.
Cause. You gave the -instance_data option on the command line. The next
token on the command line must be one of the parameters that you can specify for this
option (the possibilities are “data1”, “data2”, “data2protected“, “data2hidden”, and
“data1constant”), but eld didn’t recognize the parameter specified.
Effect. Fatal error (eld immediately stops without creating an output file).
1340 The <option name> option would be allowed if you were
making an ordinary import library, but because the DLL's on
the command line are implicit DLL's, you are instead making a
zimpimp file, in which case this option isn't allowed.
1341 <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 the
-make_implicit_lib option is specified.
1342 Unrecognized parameter to the -instance_data option.