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
Binding of References
eld Manual—527255-009
3-13
Creating Import Libraries From Existing DLLs
has unresolved references, that is either an error, warning, or ignored, depending on
what is specified for the -unres_symbols option, similar to how this option is used
when building a new loadfile. If the -unres_symbols option was not specified, the
default in this situation is error. The import library that represents the implicit DLL's
never has DWARF symbol table information.
The address of the import library that represents the implicit DLL's is specified the
same way as for the text segment of a DLL. In particular, this includes the use of a
DLL registry. The name of the entry to use in the registry file would be the same as the
filename specified in the -make_import_lib option.
Otherwise, not all the DLL's on the command line have the
EF_TANDEM_IMPLICIT_LIB bit set in their ELF headers. In this case, it is required
that there be only one DLL in the command stream, and the import library will
represent it with the same DLL name. By default, the import library created will have
the same DWARF symbols information as the existing DLL. However, if either the -s
or -x option is given, the import library will not contain DWARF symbols information.
The following are the options allowed when creating an import library that represents a
single DLL:
-must_use_iname
-no_banner
-no_verbose
-NS_extent_size
-NS_max_extents
-obey
-s
-set incomplete on
-stdin
-temp_i
-verbose
-vslisting
-warn
-x
The following are the options allowed when creating the import library that represents
the implicit DLL's:
-check_registry
-must_use_iname
-must_use_rname
-no_banner
-no_verbose
-NS_extent_size
-NS_max_extents
-obey
-stdin
-t