Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29277 Discussions

2009 Fortran Program will not compile

JohnNichols
Valued Contributor III
706 Views

Steve:

I have a program that compiled in 2009 and now gives me an MKL on the library.  I enclose the files can you tell me what I am doign wrong now.

 

I am running it on a 64 bit machine with Windows 7, VS Premium 2012 and the latest Fortran

 

Thanks jmn

0 Kudos
6 Replies
Steven_L_Intel1
Employee
706 Views
John, Please elaborate on the problem. I don't know what you mean by "gives me an MKL". The build log in the ZIP shows a successful build using 11.1 and VS2008. When I open the solution in VS2012, it builds and executes without error.
0 Kudos
JohnNichols
Valued Contributor III
706 Views
Gives me an error that : Cannot open file mkl_solver.lib and then fails to complie.
0 Kudos
Steven_L_Intel1
Employee
706 Views
That's not a compile failure, it's a link failure. The project you attached makes no reference to a mkl_solver.lib, so the project you showed here is not representative of the problem. MKL has changed its library names over the years and there is no longer an mkl_solver.lib. But your project specifies the /mkl:parallel option and the correct library names are automatically provided when the project links. I suggest finding where you manually added mkl_solver.lib and remove it, as well as the names of any other MKL libraries being used.
0 Kudos
JohnNichols
Valued Contributor III
706 Views
Steve: I went right through the program and could find no references. I deleted out the sln and vproj files and copied across the ones that worked and then ran it again, Same error. I finally thought - clean it - cleaned it and it ran. I must have had an old obj file causing the problem? Weird
0 Kudos
JohnNichols
Valued Contributor III
706 Views
Steve: I went right through the program and could find no references. I deleted out the sln and vproj files and copied across the ones that worked and then ran it again, Same error. I finally thought - clean it - cleaned it and it ran. I must have had an old obj file causing the problem? Weird
0 Kudos
Steven_L_Intel1
Employee
706 Views
Yes, you might have had an old object with an embedded linker directive that called for that library.
0 Kudos
Reply