2009 Fortran Program will not compile

2009 Fortran Program will not compile

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

Fichier attachéTaille
Télécharger morlet.zip6.49 Mo
7 posts / 0 nouveau(x)
Dernière contribution
Reportez-vous à notre Notice d'optimisation pour plus d'informations sur les choix et l'optimisation des performances dans les produits logiciels Intel.

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.

Steve - Intel Developer Support

Gives me an error that : Cannot open file mkl_solver.lib and then fails to complie.

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.

Steve - Intel Developer Support

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

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

Yes, you might have had an old object with an embedded linker directive that called for that library.

Steve - Intel Developer Support

Laisser un commentaire

Veuillez ouvrir une session pour ajouter un commentaire. Pas encore membre ? Rejoignez-nous dès aujourd’hui