Linker problem

Linker problem

Imagen de deboeck
deboeck
Dom, 07/03/2004 - 01:30



Dear,

I followed the instructions on http://www.intel.com/cd/ids/developer/asmo-na/eng/index.htmto configure Visual Studio 2003. Compiling cblas_ccopy (on of the examples included), however, fails with the following error message :

VbEen error LNK2019: unresolved external symbol _cblas_ccopy referenced in function _main
VbEen error LNK2019: unresolved external symbol _PrintVectorC referenced in function _main
VbEen error LNK2019: unresolved external symbol _GetVectorC referenced in function _main


The additional dependencies in my project settings are :

mkl_s_dll.lib mkl_p3.lib mkl_lapack.lib

The documentation on http://www.intel.com/cd/ids/developer/asmo-na/eng/index.htmdoes not really explain which additional dependencies should be included.
Do you have any idea what is going wrong ? Does there exist a (detailed) manual which explains how to configure the project settings of Visual Studio ?

Thank you very much,
Bart

RSS Superior
publicaciones de 3 / 0 nuevos
Último envío
Para obtener más información sobre las optimizaciones del compilador, consulte el aviso sobre la optimización.
Imagen de TODD R. (Intel)
TODD R. (Intel)
Mié, 10/03/2004 - 18:40


Bart,

I don't see the material you are referencing when I follow the links you provide, but perhaps I can answer some of your questions. Source for the _PrintVectorC and _GetVectorC functions is provided in the file common_func.c which can be found in the examples/cblas/source directory.

Although there isn't a detailed manual, there is some guidance for setting up your Visual C++* .NET settings at http://www.intel.com/support/performancetools/libraries/mkl/win/30486.HTM.

You are most likely getting an error with external symbol _cblas_ccopy because you are linking mkl_s.lib instead of mkl_c.lib. If you have edited your project as directed at the link above then you only need to put mkl_c.lib (or mkl_c_dll.lib) in your dependencies and you should be set.

Todd



Superior
Imagen de deboeck
deboeck
Mié, 10/03/2004 - 18:56

Dear Todd,

Thank you very much for the information. You are right, mkl_c_dll.lib should be included in the dependencies (Linker - Additional Dependencies). For some reason, Visual Studio does not 'look into' mkl_c_dll.lib to resolve the dependencies. Adding /DEFAULTLIB:mkl_c_dll.lib on the command line solves this issue (Linker - Command Line). :-)

Thanks for the PrintVector and GetVector tip !

Regards,

Bart

Superior

Inicie sesión para dejar un comentario.