<?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 Redistributing MPI runtime components in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/Redistributing-MPI-runtime-components/m-p/956931#M3101</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; We have a program in a software suite that has been built using the mpif90 compiler and need to redistribute the necessary runtime environment components with it.&amp;nbsp; There will be seperate 32 and 64 bit programs so what to include with each seems a little hairy and we just wanted to include the MPI Library Runtime installer with our installer (which runs 'Installshield').&amp;nbsp; Is this ok (read 'legal')?&amp;nbsp; If not, what's the best way to accomplish what we want to do as there seem to be various installations for different architectures?&lt;/P&gt;
&lt;P&gt;Can anyone provide some advice on this?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;-Austen&lt;/P&gt;</description>
    <pubDate>Thu, 28 Feb 2013 14:25:31 GMT</pubDate>
    <dc:creator>Austen_D_</dc:creator>
    <dc:date>2013-02-28T14:25:31Z</dc:date>
    <item>
      <title>Redistributing MPI runtime components</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Redistributing-MPI-runtime-components/m-p/956931#M3101</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; We have a program in a software suite that has been built using the mpif90 compiler and need to redistribute the necessary runtime environment components with it.&amp;nbsp; There will be seperate 32 and 64 bit programs so what to include with each seems a little hairy and we just wanted to include the MPI Library Runtime installer with our installer (which runs 'Installshield').&amp;nbsp; Is this ok (read 'legal')?&amp;nbsp; If not, what's the best way to accomplish what we want to do as there seem to be various installations for different architectures?&lt;/P&gt;
&lt;P&gt;Can anyone provide some advice on this?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;-Austen&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2013 14:25:31 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Redistributing-MPI-runtime-components/m-p/956931#M3101</guid>
      <dc:creator>Austen_D_</dc:creator>
      <dc:date>2013-02-28T14:25:31Z</dc:date>
    </item>
    <item>
      <title>The closest posted reference</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Redistributing-MPI-runtime-components/m-p/956932#M3102</link>
      <description>&lt;P&gt;The closest posted reference on this subject I can find:&lt;/P&gt;
&lt;P&gt;&lt;A href="http://software.intel.com/en-us/articles/intel-mpi-library-licensing-faq" target="_blank"&gt;http://software.intel.com/en-us/articles/intel-mpi-library-licensing-faq&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;This appears to imply that what you are suggesting is OK as of the date of that post, and I know of cases where similar usage has been approved.&lt;/P&gt;
&lt;P&gt;If you don't get an answer from one of the MPI team members, you can submit a premier issue against your MPI license requesting an answer, or you might also ask on the companion licensing forum.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2013 20:22:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Redistributing-MPI-runtime-components/m-p/956932#M3102</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2013-02-28T20:22:48Z</dc:date>
    </item>
    <item>
      <title>Hi Austen,</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Redistributing-MPI-runtime-components/m-p/956933#M3103</link>
      <description>&lt;P&gt;Hi Austen,&lt;/P&gt;
&lt;P&gt;I'm checking with our legal department right now.&amp;nbsp; I expect that you will need to have a notice that there is a component of your installation with a different EULA, but I am awaiting confirmation of this.&lt;/P&gt;
&lt;P&gt;Sincerely,&lt;BR /&gt; James Tullos&lt;BR /&gt; Technical Consulting Engineer&lt;BR /&gt; Intel® Cluster Tools&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2013 20:25:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Redistributing-MPI-runtime-components/m-p/956933#M3103</guid>
      <dc:creator>James_T_Intel</dc:creator>
      <dc:date>2013-02-28T20:25:39Z</dc:date>
    </item>
    <item>
      <title>Hi Austen,</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Redistributing-MPI-runtime-components/m-p/956934#M3104</link>
      <description>&lt;P&gt;Hi Austen,&lt;/P&gt;
&lt;P&gt;I've gotten final confirmation.&amp;nbsp; As long as you include a notice of the fact that there is a separate EULA for the Intel® MPI Library Runtime Environment and comply with the EULA terms yourself (including those in redist-rt.txt), then you should be fine.&lt;/P&gt;
&lt;P&gt;Sincerely,&lt;BR /&gt; James Tullos&lt;BR /&gt; Technical Consulting Engineer&lt;BR /&gt; Intel® Cluster Tools&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2013 21:03:07 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Redistributing-MPI-runtime-components/m-p/956934#M3104</guid>
      <dc:creator>James_T_Intel</dc:creator>
      <dc:date>2013-02-28T21:03:07Z</dc:date>
    </item>
    <item>
      <title>Excellent, Thank You James</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Redistributing-MPI-runtime-components/m-p/956935#M3105</link>
      <description>&lt;P&gt;Excellent, Thank You James&lt;/P&gt;
&lt;P&gt;-Austen&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2013 21:04:29 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Redistributing-MPI-runtime-components/m-p/956935#M3105</guid>
      <dc:creator>Austen_D_</dc:creator>
      <dc:date>2013-02-28T21:04:29Z</dc:date>
    </item>
  </channel>
</rss>

