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-27
Error Messages
Cause. You used the -r_first_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 a 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 another object file that can be
used as eld input, then don’t specify the -rld_first_L option.
Cause. You used the -limit_runtime_paths option, which affects the way NSK looks for
DLLs after it loads the program you are building, 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.
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, then don’t specify the -r option. If
your intention is to use the -r option to create another object file that can be used as
eld input, then don’t specify the -limit_runtime_paths option.
Cause. You used the -soname or -dllname option, which tells the “DLL name” to be
placed inside the DLL that you are creating, but you did not specify any option to tell
eld to build a 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 DLL, then specify an option to do that, such
as the
-dll, -shared, or -ul option. If that is not your intention, then don’t specify
the -soname or
-dllname option.
Cause. You used the -set cppdialect neutral option, which say that the program or DLL
that you are building does not need either dialect of C++, 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.
1178 The -limit_runtime_paths option is not allowed with the
-r option.
1179 The -soname or -dllname option is only allowed when you
are building a DLL.
1180 The -set cplusplusdialect option is not allowed with the
-r option.










