eld Manual

Output Listings and Error Handling
eld Manual—527255-009
6-73
Error Messages
according to the name of the “data section” in which the data was placed by the
compiler. eld considers the data sections named “.data”, “.data1”, “.sdata”, “.sdata1”,
“.bss”, and “.sbss” to all be “standard, writeable” data sections, and different copies of
a data item can be in different sections of these names without getting a complaint.
The same goes for the “standard, readonly” data sections, which are named “.rdata”,
“.srdata”, “.rodata”, “.srodata”, and “.rconst”. Any other data sections are considered
special by eld, and if a data item is in such a section then all copies of that data item
must be in a section of that same name. Similarly, different copies of a data item can’t
disagree about whether they are “writeable” or “readonly”. These rules were violated,
as shown in the message.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Did you really intend to define data items with the same name in each of
these two files, and have both definitions visible across separate compilations? If not,
change the name of one of them, or change the declaration of one of them so that it is
only visible within its own compilation. If you really do intend to have two definitions of
this data item, visible across separate compilations, then they must be the same kind
of data, as explained above. If they are different kinds of data because the two files
were created from different versions of the source code, or by using different compiler
options, repeat the compilations doing things more consistently.
Cause. A filename was specified for eld to open, but either that file doesn’t exist or
you don’t have permission to read it. This particular message can come out about the
existing program or DLL to be updated by the -alf or -strip option, or about the
file specified for the -gateway_template option, which is a special option that few
people would ever use.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Check that you spelled the name of the file correctly and that you have
permission to read it.
Cause. A filename was specified for eld to read, and the file was supposed to be a
valid TNS/E object file of some sort, but it wasn’t. In particular, this message is saying
that the file was not the ELF format, which is the format used by TNS/E object files.
This particular message can come out about the existing object file to be updated by
the -alf, -change, or -strip option, or about the file specified for the -
gateway_template file, which is a special option that few people would ever use.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Check that you spelled the name of the file correctly and that it is a valid
TNS/E object file of the type appropriate for the command that you gave.
1493 Cannot open <filename>.
1495 Specified file <filename> is not an ELF object file.