<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Intel runtime libraries and manifests in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-runtime-libraries-and-manifests/m-p/839946#M57915</link>
    <description>We are still using Intel 9.1 and have not yet upgraded to 10 seeing as we have an upcoming release.&lt;BR /&gt;&lt;BR /&gt;We had one problem recently running a program on someone's machine. It turns out that in windowssystem32 they had an old version of libifcoremd.dll or libmmd.dll (cant recall exactly which one). This was causing the application to fail to initialize. It was ery hard to find the cause of the problem.&lt;BR /&gt;&lt;BR /&gt;We mix Fortran and VS2005 C++ and Microsoft now requires you to use a manifest when your code uses MSVCR80.dll, thus making sure that your application does not incorrectly get the wrong version of that DLL (and there are multiple versions already) or that you dont have problems if people have older versions of the runtime libraries in their system32 directory.&lt;BR /&gt;&lt;BR /&gt;I am just wondering if Intel perhaps plans to take the same approach with its runtime libraries? Perhaps that is in version 10 already?&lt;BR /&gt;</description>
    <pubDate>Thu, 05 Jul 2007 19:21:54 GMT</pubDate>
    <dc:creator>van_der_merwe__ben</dc:creator>
    <dc:date>2007-07-05T19:21:54Z</dc:date>
    <item>
      <title>Intel runtime libraries and manifests</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-runtime-libraries-and-manifests/m-p/839946#M57915</link>
      <description>We are still using Intel 9.1 and have not yet upgraded to 10 seeing as we have an upcoming release.&lt;BR /&gt;&lt;BR /&gt;We had one problem recently running a program on someone's machine. It turns out that in windowssystem32 they had an old version of libifcoremd.dll or libmmd.dll (cant recall exactly which one). This was causing the application to fail to initialize. It was ery hard to find the cause of the problem.&lt;BR /&gt;&lt;BR /&gt;We mix Fortran and VS2005 C++ and Microsoft now requires you to use a manifest when your code uses MSVCR80.dll, thus making sure that your application does not incorrectly get the wrong version of that DLL (and there are multiple versions already) or that you dont have problems if people have older versions of the runtime libraries in their system32 directory.&lt;BR /&gt;&lt;BR /&gt;I am just wondering if Intel perhaps plans to take the same approach with its runtime libraries? Perhaps that is in version 10 already?&lt;BR /&gt;</description>
      <pubDate>Thu, 05 Jul 2007 19:21:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-runtime-libraries-and-manifests/m-p/839946#M57915</guid>
      <dc:creator>van_der_merwe__ben</dc:creator>
      <dc:date>2007-07-05T19:21:54Z</dc:date>
    </item>
    <item>
      <title>Re: Intel runtime libraries and manifests</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-runtime-libraries-and-manifests/m-p/839947#M57916</link>
      <description>Not in 10.0, but yes, it's being planned for the future. It's clear to us that this is the way to go, especially on Intel 64 systems where you can have a mix of 32 and 64-bit executables and relying on PATH doesn't cut it.&lt;BR /&gt;</description>
      <pubDate>Thu, 05 Jul 2007 20:34:13 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-runtime-libraries-and-manifests/m-p/839947#M57916</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2007-07-05T20:34:13Z</dc:date>
    </item>
  </channel>
</rss>

