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-55
Error Messages
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If your intention is to build a new object file out of existing files, to be able
to use this new object file as eld input, then don’t specify the name of a program on
the command line. You can’t add more stuff to an existing program, you can only
rebuild a different program from scratch. The options that you can apply to an existing
program are -alf, -change, and -strip. If you want to do one of these things,
specify the appropriate option.
Cause. You are using the Guardian version of eld, and you are building a program
that uses a user library. You specified the -local_libname option, to tell eld where
the user library currently exists, for eld to fix up refernces to it during the link.
However, the name that you specified for the -local_libname option was not a valid
Guardian filename. (This particular message comes out when you specify the -
local_libname option and you don’t also specify the -libname option. Otherwise,
a different message would appear, saying that eld could not open the file specified for
the -local_libname option, although the underlying problem would be the same.)
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you want to specify this option then you must enter a valid Guardian
filename for its parameter.
Cause. You gave the -e option more than once on the command line. This option tells
eld the name of the procedure that should be where execution begins for the program
you are building, but you specified different names at different places on the command
line. You can give this option more than once, but only if you specify the same name
each time. Also note that case is significant for this check.
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. Are you sure you want to specify the -e option at all? There usually is no
need to give this option, and specifying it is a mistake. You can validly use it to tell the
main entry point for a pTAL program, if you didn’t put the MAIN attribute into the source
code. But you must only specify one such name with -e options. Also note that, if you
misspell some other option beginning with an “e”, then eld will i
nterpret that as a “-e”
option, possibly leading to this message. There are several such options, as described
elsewhere in this manual, and you must spell them exactly as described in this manual,
except for case. Note that there is no option spelled “-elf” in eld, although there was
1329 The parameter of the -local_libname option could not be
converted to Guardian format.
1330 The -e option was given multiple times with different
procedure names: <symbol name> and <symbol name>.










