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-62
Error Messages
Recovery. This indicates some problem with the procedure for building and installing
the NSK operating system, which is beyond the scope of this document.
Cause. The -verbose, -warn, and -no_verbose options are mutually exclusive, and you
specified more than one of them. You can specify the same one of these options more
than once if you wish, but you cannot specify different ones as part of the same eld
invocation.
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. These options tell eld which messages you want to see, other than error
messages, which you cannot turn off. Decide which option you want and only specify
that one.
Cause. You specified the -check_registry or -update_registry option, to tell eld to use
a private DLL registry. Such a file did exist, and the first thing that eld tried to do with
it was to open the file for reading. However, eld could not do that, because the file
was being used exclusively by another process, perhaps by another link that was using
the -update_registry option. In this situation, eld waits and tries again, and that
should work. If that doesn’t work after a certain number of tries, then eld gives up,
resulting in this message.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Look into the status of the file that you specified. Perhaps someone has it
opened for an extended period of time in an editing session. Run eld again when it is
possible for eld to read that file.
Cause. You gave the -o option more than once on the command line, specifying
different filenames. You can give this option more than once, but only if you specify the
same filename each time.
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. This option tells the name for the main object file that eld is creating
Decide what name you want, and specify just that name on the command line. Also
note that, if you misspell some other option beginning with an “o”, then eld will
interpret that as a “-o” option, possibly leading to this message. The only other valid
1351 Conflicting verbosity options: <string> and <string>.
1353 DLL registry <filename> is in use. Giving up.
1355 Multiple specifications of the -o option with different
filenames.










