eld Manual

Output Listings and Error Handling
eld Manual—527255-009
6-119
Error Messages
Cause. You are trying to update a private DLL registry. eld first makes a new copy of
it in a temporary location, deletes the previous copy of the registry, and then renames
the temporary file to the final location. That process failed. The file has instead been
left with a different name, as shown in the message.
Effect. Warning (eld produces the registry, but not with the filename you intended).
Recovery. If you don’t have permission to delete the previous copy of the registry,
specify a different filename for the new copy. If eld succeeded in deleting the old
copy, but then could not rename the new copy, that is an operating system question
that is beyond the scope of this document.
Cause. You used the -update_registry option to tell eld the private DLL registry
to use for deciding the address of the DLL that you are creating. The private DLL
registry had an entry for that DLL already. However, the size that eld wants to reserve
in the registry for the new version of the DLL, which depends on its actual size and the
other options that you have given, is larger than the amount of space that the registry
previously reserved for this DLL. There was a block of space in the registry that was
large enough for the DLL, and eld has put it there. This might or might not be the
same starting address as before, but it definitely is a larger size than before.
Effect. Warning (eld produces the DLL, and updates the registry, but the size and
maybe also the address of the DLL has changed).
Recovery. If the new address or size is satisfactory, you don’t need to do anything.
Cause. You are trying to update a private DLL registry. eld first makes a new copy of
it in a temporary location, deletes the previous copy of the registry, and then renames
the temporary file to the final location. That process failed. You also gave the -
must_use_rname option to say that eld should consider that failure an error.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you don’t have permission to delete the existing registry, specify a
different filename for the new version of it. Or
, if there is some reason why you cannot
rename one filename to another filename in the target location (Guardian subvolume,
OSS directory, or PC folder), that could also lead to this message, but that is an
operating system question that is beyond the scope of this document..
1626 Cannot create the DLL registry <filename>; using this
name instead: <filename>.
1627 The DLL registry -range entry for this DLL is changing
from '<address> <size>' to '<address> <size>'.
1628 Cannot create DLL registry file <filename>.