<?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 Hi Tushar, in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/mpirun-command-not-found/m-p/1140193#M78243</link>
    <description>&lt;P&gt;Hi Tushar,&lt;/P&gt;

&lt;P&gt;In order to run MPI programs on&amp;nbsp;the coprocessor, you can either copy MPI libraries for the coprocessor from the host, or mount an NFS shared from the host.&lt;/P&gt;

&lt;P&gt;The first method is simpler but it consumes memory in your coprocessor. In your case, to copy MPI libraries for the coprocessor&amp;nbsp;from the host:&lt;/P&gt;

&lt;P&gt;$ sudo scp &amp;nbsp;/opt/intel/compilers_and_libraries_2016.1.150/linux/mpi/mic/bin/* mic0:/bin/&lt;/P&gt;

&lt;P&gt;$ sudo scp &amp;nbsp;/opt/intel/compilers_and_libraries_2016.1.150/linux/mpi/mic/lib/* mic0:/lib64/&lt;/P&gt;

&lt;P&gt;For more details, please refer to &lt;A href="https://software.intel.com/en-us/articles/using-intel-mpi-library-on-intel-xeon-phi-product-family"&gt;&lt;U&gt;&lt;FONT color="#0066cc"&gt;&lt;/FONT&gt;&lt;/U&gt;&lt;/A&gt;&lt;A href="https://software.intel.com/en-us/articles/using-intel-mpi-library-on-intel-xeon-phi-product-family" target="_blank"&gt;https://software.intel.com/en-us/articles/using-intel-mpi-library-on-intel-xeon-phi-product-family&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 06 Jul 2017 21:18:00 GMT</pubDate>
    <dc:creator>Loc_N_Intel</dc:creator>
    <dc:date>2017-07-06T21:18:00Z</dc:date>
    <item>
      <title>mpirun: command not found</title>
      <link>https://community.intel.com/t5/Software-Archive/mpirun-command-not-found/m-p/1140192#M78242</link>
      <description>&lt;P&gt;Hi ! I am getting "mpirun: command not found" error on my xeon PHI card. Could you please help me to solve the problem ? The response of "which mpirun" on my main procesor is :&amp;nbsp;/opt/intel/compilers_and_libraries_2016.1.150/linux/mpi/intel64/bin/mpirun.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jul 2017 12:34:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/mpirun-command-not-found/m-p/1140192#M78242</guid>
      <dc:creator>Tushar_B_</dc:creator>
      <dc:date>2017-07-04T12:34:06Z</dc:date>
    </item>
    <item>
      <title>Hi Tushar,</title>
      <link>https://community.intel.com/t5/Software-Archive/mpirun-command-not-found/m-p/1140193#M78243</link>
      <description>&lt;P&gt;Hi Tushar,&lt;/P&gt;

&lt;P&gt;In order to run MPI programs on&amp;nbsp;the coprocessor, you can either copy MPI libraries for the coprocessor from the host, or mount an NFS shared from the host.&lt;/P&gt;

&lt;P&gt;The first method is simpler but it consumes memory in your coprocessor. In your case, to copy MPI libraries for the coprocessor&amp;nbsp;from the host:&lt;/P&gt;

&lt;P&gt;$ sudo scp &amp;nbsp;/opt/intel/compilers_and_libraries_2016.1.150/linux/mpi/mic/bin/* mic0:/bin/&lt;/P&gt;

&lt;P&gt;$ sudo scp &amp;nbsp;/opt/intel/compilers_and_libraries_2016.1.150/linux/mpi/mic/lib/* mic0:/lib64/&lt;/P&gt;

&lt;P&gt;For more details, please refer to &lt;A href="https://software.intel.com/en-us/articles/using-intel-mpi-library-on-intel-xeon-phi-product-family"&gt;&lt;U&gt;&lt;FONT color="#0066cc"&gt;&lt;/FONT&gt;&lt;/U&gt;&lt;/A&gt;&lt;A href="https://software.intel.com/en-us/articles/using-intel-mpi-library-on-intel-xeon-phi-product-family" target="_blank"&gt;https://software.intel.com/en-us/articles/using-intel-mpi-library-on-intel-xeon-phi-product-family&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jul 2017 21:18:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/mpirun-command-not-found/m-p/1140193#M78243</guid>
      <dc:creator>Loc_N_Intel</dc:creator>
      <dc:date>2017-07-06T21:18:00Z</dc:date>
    </item>
  </channel>
</rss>

