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-12
Error Messages
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If your intention is to create a zimpimp file, which represents the multiple
implicit DLLs that constitute system library, or if you are trying to create an import file to
represent another (ordinary) DLL, then the names of one or more DLLs are required on
the command line. If you are not trying to do either of these things, you should not
specify the -make_import_lib option.
Cause. You are trying to create an import library. 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 import library should be created. 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 are trying to create an import library. eld first creates a workfile in the
same location (OSS directory, Guardian subvolume, or PC folder) as the place where
you specified that the import library should be created. For some reason, eld had a
problem writing to the workfile, after it had been successfully created.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Check that the indicated location isn’t in a Guardian subvolume that is full.
If that doesn’t explain the problem, it probably needs to be reported to your HP
representative.
Cause. You are trying to create an import library. eld first creates a workfile in the
same location (OSS directory, Guardian subvolume, or PC folder) as the place where
you specified that the import library should be created. For some reason, eld had a
problem writing to the workfile, after it had been successfully created.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Check that the indicated location isn’t in a Guardian subvolume that is full.
If that doesn’t explain the problem, it probably needs to be reported to your HP
representative.
1043 Cannot open output workfile <filename>.
1044 Error seeking in output file <filename>.
1045 Error writing output file <filename>.