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-21
Error Messages
Recovery. If your intention is to create a DLL to be used as an interpose user library,
then specify an appropriate option, such as -dll, -shared, or -ul, to build a DLL. If
your intention is to build some other type of object file, not a DLL, then don’t specify the
-set interpose_user_library option.
Cause. The input object files consistently used one type of floating point, i.e., either
“Tandem” or “IEEE”. On the eld command line, you specified the -set floattype option,
either saying that the file was the opposite type, or that it was neutral. That’s okay, but
eld puts out an informational message about it.
Effect. Information (This is not indicative of a problem).
Recovery. None required, assuming you know that this object file really should be
marked the way you indicated, because you know that is the type of floating point it will
really need at runtime.
Cause. The input object files contained a mixture of both types of floating point, i.e.,
“Tandem” and “IEEE”. On the eld command line, you specified the -set floattype
option, to say which type the file really was, or to say it was neutral. That’s okay, but
eld puts out an informational message about it.
Effect. Information (This is not indicative of a problem).
Recovery. None required, assuming you know that this object file really should be
marked the way you indicated, because that is the type of floating point it will really
need at runtime.
Cause. You are building a DLL, and during this link eld is also looking at various
other DLLs, and among those other DLLs eld sees that at least one says that it
requires the “Tandem” version of floating point at runtime, while another says that it
requires the “IEEE” version of floating point at runtime.
Effect. Warning (eld produces an output file, but it thinks that you might want to see
this warning about what might go wrong at runtime with other DLLs).
1141 Floating point type inconsistency. The -set floattype
option specifies <string>, but the input linkfiles imply
<string>.
1142 Floating point type inconsistency among input linkfiles.
File <filename> specifies 'tandem'. File <filename>
specifies 'ieee'.
1143 Floating point type inconsistency among input DLL's.
File <filename> specifies 'tandem'. File <filename>
specifies 'ieee'.