- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Again I am facing the same problem I had with OpenMP libarry -- after compiler upgrade (Package ID: w_ccompxe_2013.3.171 w_ccompxe_p_13.1.1.171), even though multi-threaded static IPP libraries are rinstalled on my system I am getting "missing ippcore-7.1.dl" error when I launch compiled application.
1. Haven't I already told Intel compiler engineers how wrong is to break things silently and postpone such problems to application run-time?
2. Haven't I already voiced my protest for removing static OpenMP library?
3. Why do you insist on removing our choice to produce STATICALLY LINKED SINGLE EXECUTABLE and why are you forcing us to deal with DLL hell???
The biggest WTF however is why I can even select a build option which doesn't work?!?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Sergey,
In my case this is Visual Studio 2012 Update 2 with mentioned compiler version.
If I disable use of "Use Intel Optimized Headers" then IPP static linking works -- definitely there is a problem with those headers (ippvalarray.h, valarray.h).
I can only guess that since ippvalarray.h includes ipp.h, it does not see /D _IPP_PARALLEL_STATIC defined for some reason. It is either misconfigured file or a compiler bug.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, I did not.
I have upgraded to Composer 2013 Update 4 only to confirm that I still have the same issue as with Update 3. I am working with some Intel engineers on this, will let you know once the results are in.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page