HP eld Manual page 153

Output Listings and Error Handling
after this quotation mark, and it terminated by the next quotation mark on the line, but
there was no additional quotation mark on the line.
Effect.
Fatal error (eld immediately stops without creating an output file).
Recovery. Find the offending quotation mark in the obey file. What did you intend to
have there? You may need to review the rules in the eld manual about how eld
treats quotation marks in obey files.
1282 A string starting with an equal sign is not allowed as
the parameter for the <option name> option.
Cause. You specified an option such as -L or -rpath, where the parameter is
supposed to be the name of a Guardian subvolume, OSS directory, or PC folder, or
you specified an option such as -soname, where the parameter is supposed to be a
DLL name. The parameter you specified began with an equal sign, but eld does not
allow parameters to begin with equal signs in these cases.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you really intended to give that kind of a name in these contexts, you
can't. Choose another name that doesn't begin with an equal sign.
1283 A string starting with an equal sign is only allowed as
the filename parameter for the <option name> option in the
Guardian version of eld.
Cause. You specified an option with a parameter, where the parameter began with an
equal sign. In the Guardian case this would be allowed, where eld would treat the
parameter as a "Guardian DEFINE", and expand it to a filename But, you are running
eld on the PC or on OSS, and on these platforms this type of parameter is not
allowed.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you really wanted to use a name that begins with an equal sign in this
context, you can't. On the PC or OSS, the Guardian DEFINE mechanism is not
present, so you need to directly specify the intended filename.
1284 The string <string> could not be expanded as a MAP
DEFINE.
Cause. You specified an option with a parameter, where the parameter began with an
equal sign, and you are running eld on Guardian. In this situation, eld tries to treat
the parameter as a "Guardian DEFINE". However, when eld tried to look up the name
as a Guardian DEFINE, that failed.
Effect. Fatal error (eld immediately stops without creating an output file).
eld Manual—527255-009
6-43
Error Messages