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-91
Error Messages
before seeing the filename. The message tells the line number at which this attribute
began in the file.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you specified the -public_registry option, are you sure you need to do
that? There usually is no need to give this option, because eld should be able to find
the official version of the public DLL registry automatically. If you specify this option, it
is your responsibility to provide eld with a correct public DLL registry file, and it is
beyond the scope of this manual to describe how this file should be created. If eld
could not find it on its own, and you didn’t specify the -public_registry option, then there
is something wrong with your installation. The message told the name of the file that
eld thought was the public DLL registry file. Perhaps that will help you figure out
what’s wrong.
Cause. The -public_registry option specifies the name of a public DLL registry file,
which eld uses to look up information about the operating system and other standard
DLLs when eld is creating a program or a DLL. You also used the -r option, to tell
eld to build another object file that can be used as linker input, rather than a program
or DLL.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If your intention is to create a program or DLL, then don’t specify the -r
option. If our intention is to use the -r option to create a new object file that can be
used as eld input, then don’t specify the -public_registry option.
Cause. eld uses the public DLL registry file to look up information about the operating
system and other standard DLLs. There are various ways that eld may find this file.
For example, if you are running eld on TNS/E then the operating system tells eld
where the file is. In other cases, eld looks for it in an appropriate place, expecting it to
have the name “zreg”. Or, you can override these methods by explicitly telling eld
where it is with the -public_registry option. eld did find a file by these methods, but
the file turned out not to have the proper structure for a public DLL registry file. eld
parses the contents of the file into “statements”, which in turn can have “attributes”, but
the same attribute can’t occur twice in the same statement, and this particular
message comes out when eld detected two “file” attributes in the same “dll”
statement. The message tells the line number at which this occurred in the file.
Effect. Fatal error (eld immediately stops without creating an output file).
1547 Cannot specify the -public_registry option with the -r
option.
1548 More than one file attribute in the same 'dll'
statement, at line <number> in <filename>.










