Output Listings and Error Handling
eld Manual—527255-009
6-76
Error Messages
would indicate a bug with
eld
when it created that program or DLL, and should be
reported to HP. It is also possible that the relocation table entry indicates an address in
the code segment, but you did not specify the -update_code option, to tell the
-alf
option that it was okay to update such places. There are two relocation tables, named
“.rela.dyn” and “.rela.gblzd”, and the message tells you which table had the bad entry
in it, and which entry it was. You may be able to get more information, such as the
name of the symbol being referred to, by dumping out this relocation table section with
ENOFT.
Effect.
Fatal error (
eld
immediately stops without creating an output file).
Recovery.
The -update_code option is a special option that is only intended to be
used when running
-alf
on the millicode DLL that is part of system library. If that is
the case you are doing, specify this option. Other than that case, there is probably
nothing you can do about this error message except to report it to HP as a possible
bug with
eld
when it created this program or DLL.
Cause.
This message can come out either when you give the
-alf
option, or the
-
strip
option, or the
-r
option when there is exactly one input object file.
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 new version of the file 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.
This message can come out either when you give the
-alf
option, or the
-
strip
option, or the
-r
option when there is exactly one input object file.
eld
creates
a temporary output file, before creating the real output file. When you specify the -
temp_o option,
eld
still first creates the temporary file in another place, and when that
file is created
eld
then tries to rename it to the filename specified in the -temp_o
option. That renaming failed. The temporary file that was created, and the file that you
specified in the -temp_o option, are both in the same location (Guardian subvolume,
OSS directory, or PC folder) as the place that you specified for the new version of the
file to be created.
Effect.
Warning (
eld
still creates the output object file, but not using the file you
specified with the -temp_o option as an intermediate file).
Recovery.
If you are not able to rename a file to another name in the same location
(Guardian subvolume, OSS directory, or PC folder), that is an operating system
question that is beyond the scope of this document.
1506 Cannot create workfile <filename>.
1508 Cannot create -temp_o file <filename>.
Summary of Contents for eld
Page 4: ......
Page 8: ...Contents eld Manual 527255 009 iv ...
Page 12: ...What s New in This Manual eld Manual 527255 009 viii Changes to the 527255 005 Manual ...
Page 34: ...Introduction to eld eld Manual 527255 009 1 14 Example of Use ...
Page 54: ...eld Input and Output eld Manual 527255 009 2 20 Using Archives ...
Page 98: ...Other eld Processing eld Manual 527255 009 4 20 Merging Source RTDUs ...
Page 242: ...Output Listings and Error Handling eld Manual 527255 009 6 132 Glossary of Errors ...