eld Manual

Output Listings and Error Handling
eld Manual—527255-009
6-123
Error Messages
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Assuming you really do want to specify this option, give the correct
parameter(s) to it.
Cause. You gave the -set or -change option, with the “libname” attribute, and this
requires that the next parameter on the command line be the Guardian filename that
the user library will have at runtime. However, there was no parameter at all. Either
the option occurred at the end of the command line, or the next token on the command
line began with a hyphen, meaning that it was the next option, not a parameter for the
current option.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Assuming you really do want to specify this option, give the correct
parameter(s) to it.
Cause. You specified the -set libname or -change libname option, where the
parameter that you specified for the name of the user library 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 the name to use for the user library name. 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 for a user
library name, you can’t. On the PC or OSS, the Guardian DEFINE mechanism is not
present, so you need to directly specify the intended user library name.
Cause. You specified a string directly on the command line, not as the parameter of
some option, and the string 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 command line string is not allowed.
Effect. Fatal error (eld immediately stops without creating an output file).
1640 No filename was specified for the libname attribute of
the <option name> option.
1641 A string starting with an equal sign is only allowed as
the libname attribute of the <option name> option in the
Guardian version of eld.
1642 A string starting with an equal sign is only allowed as
a command line filename in the Guardian version of eld.