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-18
Error Messages
Cause. eld prints out informational messages about some of the files that it used and
what types of files they were. In this case, it is telling you about an archive.
Effect. Information (This is not indicative of a problem).
Recovery. No action required.
Cause. eld used the archive mentioned in the message, and in more detail also tried
to use the member of the archive specified in the message, but that member was not a
valid TNS/E object file.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Perhaps there is something wrong with the archive, so that it looked like a
TNS/E archive, but didn’t have TNS/E object files in it. In that case, the process that
created the archive needs to be examined. Or, perhaps the archive has a mixture of
different types of object files in it, and you used the -all option, which tells eld to try to
use all the object files in the archive. In that case, you should build a different archive
that only contains TNS/E object files.
Cause. eld tries to create a workfile in the same location (OSS directory, Guardian
subvolume, or PC folder) as the place where you specified that the output file should
be created. For some reason, eld could not create that workfile and open it for
writing.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Check that you have permission to create files in the indicated location,
and that it isn’t a Guardian subvolume that is full.
Cause. You have given the -alf option, and in addition to the filename that was the
parameter for the -alf option you have also specified another filename on the
command line, which tells eld to use that file as the zimpimp file during this -alf
option, for resolving references to system library. However, either the file specified as
the zimpimp file doesn’t exist, or you don’t have permission to read it.
Effect. Fatal error (eld immediately stops without creating an output file).
1106 Using archive: <filename>.
1107 <archive filename>: member <member name> in archive is
not an object file.
1112 Cannot open output file <filename>: <reason>.
1117 Cannot open <filename>, the file specified to be the
zimpimp file on the -alf command line.