LNK9205001: Extra Characters Caused by One-Line Response File

ID Number: Q84733

4.x 5.0x 5.1x 5.2x 5.30 | 5.0x 5.1x

MS-DOS | OS/2

buglist5.01 buglist5.03 buglist5.05 buglist5.10 buglist5.11

Summary:

SYMPTOMS

Linking with a one-line linker response file may cause extra

characters to be displayed in the command syntax, as in the

following:

Microsoft Ò Segmented Executable Linker Version 5.30

Copyright Ó Microsoft Corp 1984-1992. All rights reserved.

Object Modules [.obj]: hello_

This problem doesn't always occur the first time LINK is run with a

one-line linker response file. It may be necessary to execute the

link command more than once to reproduce this behavior.

RESOLUTION

Although the linker displays the extra characters, it still

searches for the object module as typed in the response file. These

extra characters can be ignored.

STATUS

Microsoft has confirmed this to be a problem in LINK versions 5.01,

5.03, 5.05, 5.1, 5.11, 5.13, 5.15, 5.2, and 5.3, and QuickC Linker

versions 4.06, 4.07 and 4.1. We are researching this problem and

will post new information here as it becomes available.

More Information:

This behavior can be reproduced by creating a one-line linker response

file. For example, the following file called RESPONSE.LRF can cause

the problem even if the file HELLO.OBJ does not exist:

hello;

Then, the following command might cause the extra characters to be

displayed:

LINK @response.lrf

Additional reference words: qlink 4.10 5.10 5.20 5.30 lrf