THE ASSEMBLY PROCESS
FROM LIBRARY
6.9 LINKER ERROR HANDLING AND MESSAGES
The following error messages can be output by the Linker. The messages enclosed in question marks are output to the terminal; the other messages are only warnings and are included in the load map. If a load map is not re-quested in the command string, all messages are output to the terminal.
Message
ADDITIVE REF OF xxxxxx AT SEGMENT #yyyyyy
?/B NO VALUE?
?/B ODD VALUE?
?BADGSD?
Meaning
Rule 1 of overlay rules explained in Section 6.6 has been violated. xxxxxx represents the entry point; yyyyyy represents the segment number.
The /B switch requires an unsigned even octal number as an argument.
The argument to the /B switch was not an unsigned even octal number.
There is an error in the global symbol directory (GSD). The me is probably not a legal object module. This error message occurs on pass I of the Linker.
BAD OVERLAY AT SEG # yyyyyy Overlay tries to store text outside its region; check for a .ASECT in overlay.
yyyyyy represents the segment number.
?BAD RLD? There is an invalid relocation directory (RLD) command in the input me;
the me is probably not a legal object module. The message occurs on pass 2 of the Linker.
?BAD SWITCH? LINK did not recognize a switch specified on the first command line. On a subsequent command line, a bad switch causes this warning message but does not restart the Linker.
?BAD x SWITCH IGNORED? LINK did not recognize a switch (x) specified in the command line. The switch is ignored and linking continues.
BYTE RELOCATION ERROR AT Linker attempted to relocate and link byte quantities but failed. xxxxxx xxxxxx represents the address at which the error occurred. Failure is defined as the
high byte of the relocated value (or the linked value) not being all zero.
?CORE?
?ERROR ERROR?
?ERROR IN FETCH?
?FILE NOT FND?
?FORLIB NOT FND?
?HARD I/O ERROR?
In such a case, the value is truncated to 8 bits and the Linker continues processing.
There is not enough memory to accommodate the command or the resultant load module.
An error occurred while the Linker was in the process of recovering from a previous system or user error.
The device is not available.
Input me was not found.
The user indicated via the /F switch that the FORTRAN library, FORLIB, was to be linked with the other object modules in the command line, and the Linker could not find FORLIB.OBJ on the system device.
A hardware error occurred; try the operation again.
Message
?LDA FILE ERROR?
?/MODDVAL?
?MAP FILE ERROR?
MULT DEF OF xxxxxx
?NOINPUT?
10
IGNORED?OUTPUT FULL?
?SA V FILE ERR?
Meaning
There was a hardware problem with the device specified for LDA output or the device was full.
An odd value has been specified for the stack address. Control returns to the Linker and another command line may be indicated.
There was a hardware problem with the device specified for map output or the device is full.
The symbol, xxxxxx, was defmed more than once.
No input fIles were specified.
Overlays have been speCified in the wrong order (see overlay restrictions);
the overlay switch is ignored.
The output device was full.
The Linker encountered a problem writing the save image fIle; try the oper-ation again.
?STACK ADDRESS UNDEFINED OR IN OVERLAY?
?SYMBOL TABLE OVERFLOW?
?TOO MANY OUlPUT FILES?
The stack address specified by the
1M
switch was either undefined or in an overlay. The stack address is set to the system default.There were too many global symbols used in the program. Retry the link using the
IS
switch. If the error still occurs, the link cannot take place in the available memory.The Linker allows speCification of only two output fIles.
TRANSFER ADDRESS UNDEFINED OR IN OVERLAY
UNDEFGLBLS
UNDEFINED GLOBALS xxxxxx
xxxxxx
The transfer address was not defined or was in an overlay.
Undefmed globals exist.
The globals listed (xxxxxx) were undefined. If a load map is requested, this condition also causes the warning message, UNDEF GLBLS, to be printed on the terminal.
LIBRARIAN
The HT -11 system provides the user with the capability of maintaining libraries which may be composed of func-tions and routines of his choice. Each library is a file containing a library header, library directory (or entry point table), and one or more object modules. The object modules in a library file may be routines which are repeatedly used in a program, routines which are used by more than one program, or routines which are related and simply gathered together for ease in usage - the contents of the library file are determined by the user's needs. An example ofa typical library file is the FORTRAN library, FORLIB.OBJ. This library is provided with the FOR-TRAN package and contains all the mathematical functions needed for normal usage.
Object modules in a library file are accessed from another program via calls to their entry points; the object modules are linked with the program which uses them by the Linker (Chapter 6) to produce a single load module.
The HT-II Librarian (LIBR) allows the user to create, update, modify, list, and maintain library files.