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-110
Error Messages
together you must specify the -set process_subtype option again to resolve the
ambiguity.
Cause. It is possible to use the -r option to build a new object file that can again be
used as eld input, and when you do that you can also use the -set process_subtype
option to assign a numerical subtype to that object file. When eld is then given that
object file in a subsequent link, it copies over the subtype to its output object file again.
However, in the present link, two of the input files had subtypes assigned to them by
previous links, and the numerical values assigned in those previous links were
different, and the present link used the -set process_subtype option to resolve the
ambiguity.
Effect. Warning (eld produces an output file, but it might not be what you intended).
Recovery. If your previous links specified inconsistent process subtypes, and you
didn’t intend to do that, you should clean that up. If you do want various object files to
have different process subtypes, and sometimes to be linked together, where you
specify a -set process_subtype option to resolve the ambiguity, then you will have to
live with this warning message about it.
Cause. It is possible to use the -r option to build a new object file that can again be
used as eld input, and when you do that you can also use the -set process_subtype
option to assign a numerical subtype to that object file. When eld is then given that
object file in a subsequent link, it copies over the subtype to its output object file again.
However, in the present link, some of the input files had subtypes assigned to them by
previous links, and all those values were the same, but a different value was specified
by a -set process_subtype option in the present link.
Effect. Warning (eld produces an output file, but it might not be what you intended).
Recovery. If there was no need for the input object files to say they had a different
process subtype than what you wanted to specify for the present link, you should clean
that up. If you do want various object files to have process subtypes, and sometimes
to be linked together, where you specify a -set process_subtype option with a value
that doesn’t agree with what the input object files said, then you will have to live with
this warning message about it.
1601 Different values were specified for the process subtype
in <filename> and <filename>; the value given in the -set
process_subtype option was used.
1602 The value given in the -set process_subtype option was
used, but a different value was found in <filename>.
1603 Bad input file <filename>; this file is invalid because
the code section named <section name> is larger than 16
megabytes.










