HP eld Manual page 190

Output Listings and Error Handling
Cause. You wrote a callable procedure, and the object file produced by the compiler is
supposed to tell how many parameters it has, which should be a number between 0
and 32. However, the object file said something else.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you wrote a callable procedure with more than 32 parameters, you need
to write it a different way, because a callable procedure cannot have more than 32
parameters. The exact definition of what constitutes "one parameter" may depend on
the language and is beyond the scope of this manual. In any case, the fact that the
compiler created such a bad file is also a bug that should be reported to HP.
1519 The <option name> option is not allowed with the -r
option.
Cause. You used the <option name> option, to provide instructions to eld about
how to create the DLL or program that you are building, and you also used the -r
option, to specify eld to build another object file that can be used as a linker input,
rather than a program or a DLL.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If your intention is to create a program or a DLL, do not specify the
option. If your intention is to combine several existing object files into a new object file
that can be processed again by eld then do not specify the <option name> option.
1520 A main entry point (<symbol name>) is not allowed to be
callable.
Cause. The procedure named in the message has the CALLABLE (or
KERNEL_CALLABLE) attribute. And, you have specified that this procedure be the
main procedure where execution begins for the program that you are building, either by
using the -e option or by the fact that the procedure is marked with the MAIN attribute
in its object file. However, that combination is not allowed.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If your intention is that this procedure be the place where execution begins
for your program, then it cannot be marked CALLABLE or KERNEL_CALLABLE. If
you want your program to begin execution in privileged mode, you can accomplish that
purpose by instead giving the procedure the PRIV attribute. If you specified that this
procedure be the main entry point by giving the -e option, are you sure you wanted to
do that? In pTAL, you could do that if you forgot to put the MAIN attribute on the main
procedure, but it would probably be better for you to change the source that way, at the
same time that you change it to saying PRIV rather than CALLABLE. It is usually a
mistake to give the -e option when building a program in any other language. For
example, in C, the procedure that you call "main" is not really where execution begins,
so you should not say "-e main". Since it isn't where execution really begins, it is okay
eld Manual—527255-009
6-80
Error Messages
-r