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
eld Manual—527255-009
2-1
2 eld Input and Output
This section contains the following information:
Host Platforms - where the linker may be used.
Target Platforms - where the output from the linker may be used.
Output Object Files - what forms (libraries, loadfiles and DLLs) that output may take.
The Creation of Output Object Files - how you control the process.
Creating Segments of the Output Loadfile - how parts of a loadfile are created.
Using a DLL Registry - how you can manage DLL addressing.
Input Object Files - which files you can use as input.
Using Archives - how you can group multiple linkfiles together for eld access.
Host Platforms
The TNS/E linker (eld) runs on several platforms, as follows.
•
The TNS/E linker runs on the TNS/E version of the HP NonStop operating system,
with both the Guardian and OSS personalities.
•
The TNS/E linker runs on TNS/R versions of the HP NonStop operating system.
This means you can link PIC object files into TNS/E loadfiles as part of your
development cycle on that platform - but you will not be able to execute those
loadfiles on TNS/R.
•
The TNS/E linker runs on appropriate versions of the Windows operating system
on PC’s.
The TNS/E linker’s features are the same for all host platforms unless otherwise
specified in this manual. Differences often relate to the different types of filenames and
file characteristics on different platforms.
The Guardian namespace also exists as a subset of the OSS file system, where a
Guardian file named $a.b.c corresponds to an OSS file named /G/a/b/c.
The Guardian namespace is a set of rules use for naming files in the Guardian
filesystem. A complete description of those rules may be found in the OSS filename
(5) reference page in the OSS System Calls Reference Manual.
Those rules include:
•
The Guardian namespace ignores lowercase, the OSS namespace uses
lowercase.
•
$ and \ are not recognized in the OSS namespace
•
If a filename contains a period in it, and a file of that name is to be created in a
Guardian subvolume, the period is deleted from the name.