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

Introduction to eld
eld Manual—527255-009
1-2
Example Command Line
Example Command Line
The following is an example of a linker command line:
eld myobj1 myobj2 -o myprog -lib mydll
This command specifies linkfiles myobj1 and myobj2 as inputs to the linker, which is
named eld. The linker will combine them into the program named myprog, and will
bind references against a DLL found from mydll.
For a longer example of using eld, see the Example of Use on page 1-9.
eld Functionality
eld can also :
•
obtain its input linkfiles from archives.
•
combine existing linkfiles into a new linkfile with the -r option.
•
create an import library, including one that represents all the “implicit” libraries.
•
bind references against user libraries and import libraries.
•
update an existing loadfile with the -alf, -change, and -strip options.
The linker does not have a programmatic interface other than starting it as a new
process, providing it the appropriate inputs, and looking at the outputs that it produces.
There are various ways of invoking the linker, such as directly from the command line,
indirectly from other command line tools such as the C compiler, or through graphical
user interfaces. You can run eld in these ways:
Manually, at a command prompt.
Automatically, when using these compilers:
This publication explains only how to run eld manually. For information on running eld
automatically, see:
Environment Compiler
Guardian CCOMP
CPPCOMP
ECOBOL
OSS c89
c99
ecobol
Windows NT*
Windows 2000*
Windows XP*
All of the above and eptal
* By means of the Cross-Compiler CDs, ETK










