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-11
Error Messages
Recovery. If your intention is to create a zimpimp file, then the other filenames on the
command line should be implicit DLLs. If your intention is to create an import library to
represent an ordinary DLL (not one of the implicit DLLs), then correct your command
line syntax, because there are more filenames present than is allowed. If it is not your
intention to create any kind of import library then don’t give the -make_import_lib
option.
Cause. You specified the -make_import_lib option, telling the name of the import
library that you want to create, and you also specified one other filename on the
command line. That means that you are creating an import library to represent some
other (ordinary) DLL. The other filename you put on the command line should be the
DLL to be represented. It wasn’t a DLL, so that’s an error.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If your intention is to create an import library to represent a single
(ordinary) DLL, then the other filename on the command line should be that DLL. If
you are not trying to create an import library, then don’t specify the -make_import_lib
option.
Cause. You specified the -make_import_lib option, in order to create the zimpimp file
that represents the multiple implicit DLLs that constitute system library, and you also
specified those implicit DLLs on the command line. There are some symbols that
legitimately exist in more than one of the implicit DLLs, because they are specially
marked by the C++ compiler, but other symbols may only come up in one of the implicit
DLLs. The indicated symbol was illegally present in more than one of the implicit
DLLs, so this is an error.
Effect. Error (The linker immediately stops).
Recovery. This indicates some problem with the procedure for building and installing
the NSK operating system, which is beyond the scope of this document.
Cause. You specified the -make_import_lib option, telling the name of the import
library that you want to create, but you didn’t specify any other filenames on the
command line. That is an error.
1026 The -make_import_lib option was given, so the other
filename on the command line should be a DLL, but <filename>
is not a DLL.
1041 The symbol named <symbol name> was found both in
<filename> and in <filename>.
1042 The -make_import_lib option was specified, but there
were no other filenames on the command line to tell the
DLL(s) to use as inputs.