Compiling with /Qtcheck generates weird link error

[fjeske]

I'm using VS 2005 and IVF 10.1.021 and have just tried to add /Qtcheck to my Fortran compiles to be able to use the Intel Thread Checker but am getting a strange link error:

ipo: error #11035: Fatal error cannot open libassuret40
Link: error error_during_IPO_compilation: problem during multi-file optimization compilation (code 1)
Link: error error_during_IPO_compilation: problem during multi-file optimization compilation (code 1)

I only modified the compiler options so I don't know where the reference to libassuret40 came from. It turns out this lib is in the installed VTune distribution which I then added to the link line to no avail. My program otherwise compiles and links OK without /Qtcheck on the compile line.

As a test, I copied my entire link step to a separate dir, created a makefile and, oddly, found that it linked OK. Anyone have any idea why this happens under VS 2005, however?

[TimP]

I believe libassuret40 isthe debugging version of the OpenMP support library. It should come from the thread checker installation, or VTune, if thread checker installed it there. Thatlibrary path should be in your environment or command line options. IPO should be disabled, and debug options set automatically, by /Qtcheck.

Did you try to use the dynamic instrumentation scheme for thread checking onyour standardbuild? That way seems to have had the most effort put into it lately.

Maintenance of thread checker seems to be partly on hold, pending a new version, and I've had to hold back on use of it. Iguess the emphasismay shift to VS2008.

[Yuan_C_Intel]

Quoting - michele.delsolmicrosigma.fr

I am getting the same error with Intel C++ 11.1 and TChecker 3.1 Visual C++ 2008 - libassert40.lib not found. If I add it to the linker additional dependencies, it fixes that problem but then I get a really weird c:Program.obj not found error from the linker;

I then compiled without /Qtcheck and did get error reporting from Thread Checker with drill down all the way to the source of the application.

Michle

Hello,

The option needs vtune library to perform thread analysis.
Pleasetry following:
Open the project property page -> Linker -> General
In the "Additional library Directory", add your vtune lib path, such as: C:Program FilesIntelVTuneAnalyzerLib"

Thank you.