<?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 The performance library path in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/static-executables-in-2015/m-p/1047636#M114496</link>
    <description>The performance library path is set when setting up to compile.  Later if you run without that set-up you would need path set-up as Steve said.</description>
    <pubDate>Thu, 06 Nov 2014 15:59:16 GMT</pubDate>
    <dc:creator>TimP</dc:creator>
    <dc:date>2014-11-06T15:59:16Z</dc:date>
    <item>
      <title>static executables in 2015</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/static-executables-in-2015/m-p/1047633#M114493</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I need to run multiple copies of my code on my computer while compiling &amp;amp; linking.&amp;nbsp; It appears that in Fortran 2015 I can no longer use portlib to make portable/static code.&amp;nbsp; I get entry point errors in the MKL DLL which I suspect is just the start of my troubles with multi-threaded OpenMP &amp;amp; MKL code. What is the easiest way to make code to move around my computer?&amp;nbsp; I read the documentation but it seemed way too complex for what I'm trying to do.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Nov 2014 08:36:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/static-executables-in-2015/m-p/1047633#M114493</guid>
      <dc:creator>Bruce_Weaver</dc:creator>
      <dc:date>2014-11-06T08:36:48Z</dc:date>
    </item>
    <item>
      <title>Apparently, the default</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/static-executables-in-2015/m-p/1047634#M114494</link>
      <description>&lt;P&gt;Apparently, the default changed with the 2015 release, and you would need to select /MT one way or another to get the previous behavior.&amp;nbsp; It didn't occur when I first saw your post that this might be your question.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Nov 2014 12:50:46 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/static-executables-in-2015/m-p/1047634#M114494</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2014-11-06T12:50:46Z</dc:date>
    </item>
    <item>
      <title>The default changed in 2013</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/static-executables-in-2015/m-p/1047635#M114495</link>
      <description>&lt;P&gt;The default changed in 2013 SP1 (14.0). You can still link statically if you want. In Visual Studio, the property is Fortran &amp;gt; Libraries &amp;gt; Runtime Library &amp;gt; Multithreaded (not Multithread DLL). Most of the Fortran libraries are available in static form - OpenMP and coarray support are DLL only.&lt;/P&gt;

&lt;P&gt;Perhaps the real problem here is that as of 2013 SP1, the Intel performance libraries (MKL, TBB, IPP) aren't added to PATH by default and you have to add the paths to their DLLs yourself. For Fortran, that's just MKL. Moving programs around on a computer with Fortran installed is not a problem - the only issue is when you take the executable to another computer.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Nov 2014 14:48:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/static-executables-in-2015/m-p/1047635#M114495</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2014-11-06T14:48:02Z</dc:date>
    </item>
    <item>
      <title>The performance library path</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/static-executables-in-2015/m-p/1047636#M114496</link>
      <description>The performance library path is set when setting up to compile.  Later if you run without that set-up you would need path set-up as Steve said.</description>
      <pubDate>Thu, 06 Nov 2014 15:59:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/static-executables-in-2015/m-p/1047636#M114496</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2014-11-06T15:59:16Z</dc:date>
    </item>
    <item>
      <title>It's set up to build, yes.</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/static-executables-in-2015/m-p/1047637#M114497</link>
      <description>&lt;P&gt;It's set up to build, yes. But the paths to the MKL DLLs are not added to PATH when the compiler is installed.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Nov 2014 17:01:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/static-executables-in-2015/m-p/1047637#M114497</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2014-11-06T17:01:19Z</dc:date>
    </item>
  </channel>
</rss>

