Intel® Fortran Compiler

cannot open file libucrt.lib


I used to have on my old computer the Intel Visual Fortran Composer XE 2011, integrated with Microsft Visual Studio 2010, and with IMSL 6.

Now I have upgraded to the Intel Parallel Studio XE Composer Edition for Fortran Windows* with Rogue Wave* IMSL* 7.0.

What is happening is that now, some of my Fortran programs are not compilling. It gives me the following error:

fatal error LNK1104: cannot open file libucrt.lib

Do you know why this happens? can you help?


Intel® Parallel Studio XE 2016 Composer Edition and Intel® System Studio 2016 Compiler Fixes List

Defects and feature requests described below represent specific issues with specific test cases. It is difficult to succinctly describe an issue and how it impacted the specific test case. Some of the issues listed may impact multiple architectures, operating systems, and/or languages.
  • C/C++
  • Fortran
  • 英特尔® Parallel Studio XE Composer Edition
  • 英特尔® C++ 编译器
  • Intel® Fortran Compiler
  • Optimizer bug

    The following test program gives incorrect results when options such as /Ot, /O2, /fast are used on Windows 8.1 with the 32 and 64-bit IFort compiler version Some earlier versions of the compiler, such as 11.1.070, give correct results whether or not optimization is requested.

    Code Coverage for static library

    Hi, I wondered if anyone had used the Intel codecov tool for analysis of a static library.

    I am building a static library comprising mainly algorithmic content which I want to analyse and also have a driver program which is used to test the library. The driver is linked against a static .lib. If I follow the examples in the documentation and compile everything with /Qcov-gen I get a dyn file in the exe directory and when I use the tools on that it gives me coverage analysis for the exe not for the library. However it is the library I am most interested in.

    open file using newunit directive, threadsafe fortran

    HI Lorri, others,

    I have just one more question before I dive in and try to play

    with rewriting parts of my application for threadsafe, and it

    relates to reading the input data.  

    Each thread independently processes in the same way , without any sharing

    of results between the threads, data from the single data file submitted to the thread.

    The file is identified by a full path, such as c:\mydatafiles\exmpl001.dat as the first argument from the c== calling interface

    订阅 Intel® Fortran Compiler