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-13
Error Messages
Cause. You are trying to create an import library on Guardian, and after creating the
import library eld tried to set its file code to 800, but was unable to do so.
Effect. Error (The linker cannot do what was requested of it and stops, deleting the file
that had been created up to that point).
Recovery. If you are not able to set the file code of a file, that is an NSK question that
is beyond the scope of this document.
Cause. This message comes out after message 1046 (see above). It means that,
after being unable to set the file code of the file, and then trying to delete the file, eld
was also unable to delete the file.
Effect. Fatal error (eld immediately stops, and the output file has not been deleted).
Recovery. If you are not able to delete a file that you just created, that is an operating
system question that is beyond the scope of this document.
Cause. When you specify the -temp_i option, eld still first creates a temporary file
in another place, and when that file is created eld then tries to rename it to the
filename specified in the -temp_i option. That renaming failed.
Effect. Warning (eld still creates the import library, but not using the file you
specified with the -temp_i option as an intermediate file).
Recovery. If you are not able to rename a file to another name in the same location
(Guardian subvolume, OSS directory, or PC folder), that is an operating system
question that is beyond the scope of this document.
Cause. You are trying to create an import library. eld first creates it in a temporary
location, deletes any file that previously existed with the name specified for the import
library, and then renames the temporary file to the final location. That process failed.
The file has instead been left in the place that the message calls the “object file
name”.
Effect. Warning (eld produces an output file, but not with the filename you intended).
1046 Could not set file code; deleting import library
<filename>.
1047 Error attempting to delete file <filename>.
1048 Cannot create -temp_i file <filename>.
1049 Cannot create -make_import_lib file <filename>; object
file name: <filename>.










