Conference nicctr::kap-users

370.0. "Tip: Lost Linker in NT" by PERFOM::HENNING () Wed Mar 12 1997 16:28

    After you installed KAP under NT, did you lose your linker?   If so,
    here's how to find it again.
    
    Symptoms:
    
       After defining the KAP environment variables, for example by typing 
       
           e:\dec\kapf\kapf_env
    
       the system cannot find the linker:
    
           kf77 tmp.f
            KAP/ALPHA_NT_F   1.0 k212118 940901     12-Mar-1997   16:16:57
           0 errors in file tmp.f
           DEC (R) Fortran Optimizing Compiler Version: V1.2
           Copyright (c) 1996 Digital Equipment Corp. All rights reserved.
           
           f77: error: File 'link' not in path
           compiler spawn failure: No error
    
       If you type in a link command by hand, it also fails:
    
           link
           The name specified is not recognized as an
           internal or external command, operable program or batch file.
    
        Examining the path (e.g. with "echo %path%" or "set p") yields no
        apparent clues.       
    
    
    Workaround:
    
        The cause of this problem appears to be the trailing space in
        the line 
    
                set path=E:\DEC\KAPF;%path% 
    
        in the file 
    
                (device):\dec\kapf\kapf_env.bat
    
        Edit that file with the editor of your choice and remove the
        trailing space.
    
    
    Hypothesized cause:
    
       The new support for extended filenames in NT has to do some fancy
       tricks to handle some of the interesting file names that are now
       allowed, such as e:\program files\devstudio\vc\bin.  It seems likely
       that this code has one bug or another in how it figures out when to
       pay attention to a space character, when to ignore it, when to print
       it, and when to accept it on input.  Don't give it extra spaces when
       you don't need to.