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-26
Error Messages
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If your intention is to combine one or more existing object files into a new
object file, put their names on the command line. If you want to do something else,
such as stripping the symbols from an existing object file (for example), you need to
put the appropriate option for that purpose on the command line, and of course you
need to spell it correctly.
Cause. You specified one of the -temp_i, -temp_o, or -temp_r options, to tell the
name that eld should use for an intermediate file during the process of creating some
other file, as shown in the message. You also specified the name of the temporary file
as a qualified name (not a simple name). When you do that, the name that you
specified for the temporary file is required to be in the same location (Guardian
subvolume, OSS directory, or PC folder) as the final file that you are trying to create,
and you must spell them both exactly the same way for eld to understand this. But,
the locations didn’t match.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you really want to use the -temp_* option, there is no need to specify a
fully qualified name. You can just specify a simple name, and then eld will put it in the
right place. But you probably also have no need for the -temp_* option at all, so you
can just omit it.
Cause. You used the -rpath or -rld_L option, to specify a place where NSK will
look for DLLs at runtime, and you also used the -r option, to tell eld to build another
object file that can be used as linker input, rather than a program or DLL.
Effect. Error (The linker cannot do what was requested of it and will eventually stop,
but may continue for the purpose of detecting additional errors before stopping).
Recovery. If your intention is to create a program or DLL, then don’t specify the -r
option. If your intention is to use the -r option to create an object file that can be used
again as eld input, then don’t specify the -rpath or -rld_L option.
1174 Output file <filename> and temporary file <filename>
must be in the same directory/subvolume (and spelled the same
way on the eld command line).
1176 The -rpath or -rld_L option is not allowed with the -r
option.
1177 The -rld_first_L option is not allowed with the -r
option.










