kmp_import.obj and vc90.pdb link warning in Visual Studio 2010

John_Young · ‎04-15-2013

Hi,

I have Composer XE 2013 Update 3 installed with Visual Studio 2010 on Windows 7. When I try to link the MKL libraries I get thefollowing link warning

libiomp5md.lib(kmp_import.obj) : warning LNK4099: PDB 'vc90.pdb' was not found with 'libiomp5md.lib(kmp_import.obj)' or at 'C:\Users\j2\Desktop\test\test_application\x64\Release\vc90.pdb'; linking object as if no debug info

If I dump out the libiomp5md library with

lib /extract:kmp_import.obj "C:\Program Files (x86)\Intel\Composer XE\compiler\lib\intel64\libiomp5md.lib"

and then

dumpbin /section:.debug$T /rawdata kmp_inport.obj

I see

RAW DATA #4
00000000: 04 00 00 00 6A 00 15 15 40 59 B2 DA 95 D4 09 4F ....j...@Yｲﾚ.ﾔ.O
00000010: A9 54 FD A7 94 D4 F3 25 21 00 00 00 4F 3A 5C 70 ｩTｧ.ﾔ・!...O:\p
00000020: 72 6F 6D 6F 5C 32 30 31 33 30 32 32 37 5C 74 6D romo\20130227\tm
00000030: 70 5C 77 69 6E 5F 33 32 65 2D 72 74 6C 5F 35 5F p\win_32e-rtl_5_
00000040: 6E 6F 72 5F 64 79 6E 2E 31 32 2E 72 65 6C 2E 34 nor_dyn.12.rel.4
00000050: 30 2E 72 31 2E 63 30 2E 74 30 2D 66 78 65 6F 77 0.r1.c0.t0-fxeow
00000060: 69 6E 31 37 5C 76 63 39 30 2E 70 64 62 00 F2 F1 in17\vc90.pdb.

I think the link error is caused by the vc90.pdb being embedded in libiomp5md.lib since Visual Studio 2010 creates a vc100.pdb file. Visual Studio 2008 creates a vc90.pdb file.

Is there a way to prevent this link warning? If possible, I would prefer to solve the issue instead of just suppress the warning. Why is vc90.pdb embedded in libiomp5md.lib in the first place?

Thanks,

John

SergeyKostrov · ‎04-15-2013

>>...Is there a way to prevent this link warning?.. I think the only way to get rid of that warning is to recompile the library with Visual Studio 2010. But, it is possible that when Visual Studio 2012 is used it will be displayed again. Note: This is just a warning and I ignore similar warnings related to different Microsoft libraries for Windows CE platforms for many years. There are No any problems and applications work.

John_Young · ‎04-16-2013

>> I think the only way to get rid of that warning is to recompile the library with Visual Studio 2010. But, it is possible that when Visual Studio 2012 is used it will be displayed again.

Thanks. I guess I'll hvae to ignore it for now.

Does the pdb file name need to be embedded in the object file at all? Unless it's required to be there, I'm not sure what benefit is being added to MKL by having it there.

SergeyKostrov · ‎04-16-2013

>>...Does the pdb file name need to be embedded in the object file at all?.. Of course No. It actually could be removed in Linker Settings of a Visual Studio project ( only MKL software engineers could change it ).

Andrey_C_Intel1 · ‎04-18-2013

Hi John,

Thank you for reporting the issue, it will be fixed in the next release of Intel compiler.

Regards,
Andrey

John_Young · ‎04-18-2013

Andrey and Sergey,

That's great. Thanks for your help.

John