<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated on Wed, 25 Nov 2009 08:50:29 -0800 -->
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <atom:link href="http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/feed/" rel="self" type="application/rss+xml" />
    <title>Intel Software Network Comments feed</title>
    <link>http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/feed/</link>
    <description></description>
    <language>en-us</language>
    <item>
      <title>By Akio Yasu (Intel)</title>
      <description><![CDATA[ Here is the additional information.

There are a few workarounds and solution on this issue.
1) Rebuild the OepnCV library with libiomp5 library, so no more library conflict happens.
2) Delete IPP PATH from system environment variable or runtime environment not to have OpenCV try to use IPP libraries.
3) Set KMP_DUPLICATE_LIB_OK=TRUE environment variable to ignore the library conflict, which is not really recommended to do though.
4) Use the latest OpenCV whose version is 1.1pre1. This versioned library is built with Microsoft OpenMP library “vcomp.dll” which is compatible with Intel OpenMP library “libiomp5md.dll”. So we can use OpenCV + IPP6.x without any errors.
 ]]></description>
      <link>http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-17964</link>
      <pubDate>Tue, 03 Feb 2009 11:28:12 -0800</pubDate>
      <guid isPermaLink="true">http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-17964</guid>
    </item>
    <item>
      <title>By Ying Hu (Intel)</title>
      <description><![CDATA[ Akio, thank you a lot. I add the information you provided in the article.  ]]></description>
      <link>http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-18038</link>
      <pubDate>Wed, 04 Feb 2009 21:24:25 -0800</pubDate>
      <guid isPermaLink="true">http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-18038</guid>
    </item>
    <item>
      <title>By 胡英 (Intel)</title>
      <description><![CDATA[ See the related acticles at Intel Compiler KB

<<http://software.intel.com/en-us/articles/omp-error-15-initializing-libguidelib-but-found-libguide40dll-already-initialized/>>

<<http://software.intel.com/en-us/articles/omp-error-15-initializing-libguidedylib-but-found-libiomp5dylib-already-initialized/>>
 ]]></description>
      <link>http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-22556</link>
      <pubDate>Mon, 13 Apr 2009 20:39:17 -0700</pubDate>
      <guid isPermaLink="true">http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-22556</guid>
    </item>
    <item>
      <title>By Santhosh</title>
      <description><![CDATA[ I still have the problem, I deleted  libguide40.dll. I built the OpenCv project once again. ]]></description>
      <link>http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-31212</link>
      <pubDate>Thu, 17 Sep 2009 20:20:14 -0700</pubDate>
      <guid isPermaLink="true">http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-31212</guid>
    </item>
    <item>
      <title>By Intel Software Network Support</title>
      <description><![CDATA[ Hello Santhosh,

To obtain further support for this, please post this issue to the Intel(R) IPP forum, as support is not typically available in the page comments.

-Lexi
Intel(R) Software Network Support
 ]]></description>
      <link>http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-31237</link>
      <pubDate>Fri, 18 Sep 2009 09:32:41 -0700</pubDate>
      <guid isPermaLink="true">http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-31237</guid>
    </item>
    <item>
      <title>By gary-oberbrunner</title>
      <description><![CDATA[ This is a serious problem.  My product is a plug-in; I link with Intel libs, and the host app may also link with Intel libs.  I have no control over what the host does.  There needs to be a solution that doesn't require the host to change.  (I've submitted an issue already.)  Changing a lib's name in an incompatible way, and causing the app to exit on an error, are both extremely bad practice IMHO.  Did I miss some discussion last year or two years ago that this was going to screw my customers? ]]></description>
      <link>http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-32268</link>
      <pubDate>Wed, 07 Oct 2009 10:11:24 -0700</pubDate>
      <guid isPermaLink="true">http://software.intel.com/en-us/articles/opm-abort-initializing-libguide40dll/#comment-32268</guid>
    </item>
  </channel></rss>