The information in this article applies to:
SYMPTOMSAn attempt to link an application with a one-line linker response file causes extra characters to display in a command prompt, as in the following example: Microsoft (R) Segmented Executable Linker Version 5.30This problem does not always occur the first time LINK runs with a one-line linker response file. More than one attempt may be required to reproduce this behavior. RESOLUTIONEven though LINK displays the additional characters, it searches for the correct object file name as specified in the response file. It is safe to ignore the extra characters. STATUSMicrosoft has confirmed this to be a problem in LINK versions 5.01, 5.02, 5.03, 5.05, 5.1, 5.11, 5.13, 5.15, 5.2, 5.3, and 5.31 for MS-DOS, LINK versions 5.01, 5.02, 5.03, 5.05, 5.1, 5.11, 5.13, and 5.15 for OS/2, and QuickC linker versions 4.06, 4.07, and 4.1 for MS-DOS. This problem was corrected in LINK version 5.5 for MS-DOS. MORE INFORMATIONTo reproduce this behavior, create a linker response file that contains only one line of text. For example, create a file called RESPONSE.LRF that contains the following line of text: hello;LINK exhibits the behavior described above even if HELLO.OBJ does not exist. To demonstrate this problem, enter the following at the operating system command prompt: LINK @response.lrf Additional query words: qlink lrf 4.10 5.01.20 5.01.21 5.02 5.03 5.05 5.10 5.11 5.13 5.15 5.20 5.30 5.31.009
Keywords : kb16bitonly |
Last Reviewed: October 28, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |