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-3
Linker Version Information
•
C/C++ Programmer’s Guide
•
HP COBOL For NonStop Systems
eld runs in the following environments:
•
Guardian
•
OSS
•
Windows NT, Windows 2000, and Windows XP, using either the Cross-Compiler
CDs or the HP Enterprise Toolkit—NonStop Edition (ETK), which is based on
Microsoft Visual Studio .NET
Linker Version Information
eld writes information about its version number into the .tandem_info section of its
output object file.
eld also contains a VPROC procedure that is a standard feature of Tandem tools.
The PC version of eld contains version information that you can see by looking at the
"properties" of the eld.exe file.
Native Object Files
eld operates on TNS/E native object files. Native object files are in Executable and
Linking Format (ELF), a standard format used for object files, with some HP
extensions.
This manual presents only basic information about these files. For details on the
structure of native object files for TNS/E, see Appendix A, TNS/E Native Object Files
and the enoft Manual.
Native object files are either Linkfiles or Loadfiles, but not both.
The native compilers create native object files called linkfiles from source code.
eld produces native object files called loadfiles from such linkfiles.
Native object files of TNS/E in the Guardian environment have a file code of 800.
Native object files of TNS/R in the Guardian environment have a file code of 700.
Note. eld has the same capabilities and syntax in each environment, but each environment
has its own rules, for example, filename syntax.
Can Be Linked to Produce a Loadfile Can Be Executed
Linkfiles Yes No
Loadfiles No Yes