Knowledge Base

BUG: Environment Compiler Options Incorrectly Take Precedence

PSS ID Number: 149510

Article Last Modified on 11/3/1999


The information in this article applies to:


This article was previously published under Q149510

SYMPTOMS

Compiler options set with the FL32 environment variable incorrectly take precedence over like compiler options set either in the Developer Studio workbench or at the MS-DOS command-line prompt.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The correct compiler option precedence should be that any like compiler options specified in the Developer Studio workbench or those used on the MS- DOS command-line prompt take precedence over similar compiler options set in the FL32 environment variable.

Steps to Reproduce Problem

  1. Set the FL32 environment variable to the /G3 compiler option. At an MS-DOS command prompt type:

    SET FL32=/G3.

  2. Compile the sample code code provided using the /G4 compiler option. At the same MS-DOS command-line prompt, type:

    FL32 /G4 test.for.

Note that the compiler discards the /G4 option using the /G3 option instead and displays the following warning message:
Command line warning D2005: flag /G4 conflicts with earlier flag.
Flag ignored.

Sample Code

C Compile options needed: none
      print *, 'hello, world'
      end
				

Additional query words: 4.00

Keywords: kbCompiler KB149510
Technology: kbAudDeveloper kbFORTRANPower400NT kbFortranSearch kbZNotKeyword8