<?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 Kevin, thanks for your help, in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943253#M17615</link>
    <description>&lt;P&gt;Kevin, thanks for your help,&lt;/P&gt;
&lt;P&gt;I'm reading pg. 21 in "&lt;A href="http://software.intel.com/en-us/articles/configuring-intel-xeon-phi-coprocessors-inside-a-cluster"&gt;Configuring Intel® Xeon Phi™ coprocessors inside a cluster&lt;/A&gt;" ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;and I see the command to build zlib, now, excuse me for the newbie questions but:&lt;/P&gt;
&lt;P&gt;a. should I run those commands on the Phi (after ssh'ing into it),&amp;nbsp;&lt;/P&gt;
&lt;P&gt;or are they being run on the host ? (which somehow copies them into the uOS environment&lt;/P&gt;
&lt;P&gt;which is in&amp;nbsp;/opt/crtdc/micgnu/)&lt;/P&gt;
&lt;P&gt;b. is there even a way to install Intel Compiler on the Xeon Phi itself? should I even do it in case the main program should&lt;/P&gt;
&lt;P&gt;only be run on the Phi and not compiled on it?&lt;/P&gt;
&lt;P&gt;Thank you very much once again,&lt;/P&gt;
&lt;P&gt;Chen&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 07 Jul 2013 13:20:54 GMT</pubDate>
    <dc:creator>Chen_S_1</dc:creator>
    <dc:date>2013-07-07T13:20:54Z</dc:date>
    <item>
      <title>Anyone compiled zlib for MIC ?</title>
      <link>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943249#M17611</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;
&lt;P&gt;I'm compiling a static library for Xeon Phi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;and this library uses &amp;nbsp;'zlib compression' library (&amp;nbsp;&lt;A href="http://www.zlib.net/"&gt;http://www.zlib.net/&lt;/A&gt;&amp;nbsp;) .&lt;/P&gt;
&lt;P&gt;When I try to build zlib on my CentOS computer (which contains the Xeon Phi),&lt;/P&gt;
&lt;P&gt;I keep getting errors during 'make test' which are shown in the .log file attached.&lt;/P&gt;
&lt;P&gt;I've tried 2 configure command, both showed the same errors :&lt;/P&gt;
&lt;P&gt;1) CC=icc CFLAGS="-mmic" CHOST=x86_64 ./configure&lt;/P&gt;
&lt;P&gt;2) CC=icc CFLAGS="-mmic" CHOST=x86_64 ./configure --sharedlibdir=/opt/intel/composer_xe_2013.5.192/compiler/lib/intel64&lt;/P&gt;
&lt;P&gt;I would love some advice&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Chen&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jul 2013 08:16:29 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943249#M17611</guid>
      <dc:creator>Chen_S_1</dc:creator>
      <dc:date>2013-07-07T08:16:29Z</dc:date>
    </item>
    <item>
      <title>The document available under</title>
      <link>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943250#M17612</link>
      <description>&lt;P&gt;The document available under &lt;A href="http://software.intel.com/en-us/articles/configuring-intel-xeon-phi-coprocessors-inside-a-cluster"&gt;Configuring Intel® Xeon Phi™ coprocessors inside a cluster&lt;/A&gt; includes instructions for &lt;STRONG&gt;Compiling native GNU tools&lt;/STRONG&gt; which includes zlib and other GNU tools.&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jul 2013 08:37:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943250#M17612</guid>
      <dc:creator>Kevin_D_Intel</dc:creator>
      <dc:date>2013-07-07T08:37:27Z</dc:date>
    </item>
    <item>
      <title>Please explain something to</title>
      <link>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943251#M17613</link>
      <description>&lt;P&gt;Please explain something to me,&lt;/P&gt;
&lt;P&gt;if I only wish to compile zlib on the host PC, not on the Phi itself,&lt;/P&gt;
&lt;P&gt;and have it built as a MIC binary (so I could then build my main library which depends&lt;/P&gt;
&lt;P&gt;on zlib,&amp;nbsp;and copy it to uOS),&lt;/P&gt;
&lt;P&gt;is there a shorter way ?&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jul 2013 10:37:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943251#M17613</guid>
      <dc:creator>Chen_S_1</dc:creator>
      <dc:date>2013-07-07T10:37:37Z</dc:date>
    </item>
    <item>
      <title>The issue is configure. If</title>
      <link>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943252#M17614</link>
      <description>&lt;P&gt;The issue is configure. If the app did not depend on its operation and instead the code could simply be compiled/linked then compilation on the host with &lt;STRONG&gt;-mmic&lt;/STRONG&gt; would do the job.&lt;/P&gt;
&lt;P&gt;There is another similar procedure contributed by a customer discussed on &lt;A href="http://software.intel.com/en-us/articles/cross-compilation-challenges"&gt;Cross-compilation challenges&lt;/A&gt;&amp;nbsp;but it isn't any shorter than the earlier cited method.&lt;/P&gt;
&lt;P&gt;The only other shorter method would be if someone provided a pre-built zlib for native that you could simply use to build your library.&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jul 2013 11:45:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943252#M17614</guid>
      <dc:creator>Kevin_D_Intel</dc:creator>
      <dc:date>2013-07-07T11:45:00Z</dc:date>
    </item>
    <item>
      <title>Kevin, thanks for your help,</title>
      <link>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943253#M17615</link>
      <description>&lt;P&gt;Kevin, thanks for your help,&lt;/P&gt;
&lt;P&gt;I'm reading pg. 21 in "&lt;A href="http://software.intel.com/en-us/articles/configuring-intel-xeon-phi-coprocessors-inside-a-cluster"&gt;Configuring Intel® Xeon Phi™ coprocessors inside a cluster&lt;/A&gt;" ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;and I see the command to build zlib, now, excuse me for the newbie questions but:&lt;/P&gt;
&lt;P&gt;a. should I run those commands on the Phi (after ssh'ing into it),&amp;nbsp;&lt;/P&gt;
&lt;P&gt;or are they being run on the host ? (which somehow copies them into the uOS environment&lt;/P&gt;
&lt;P&gt;which is in&amp;nbsp;/opt/crtdc/micgnu/)&lt;/P&gt;
&lt;P&gt;b. is there even a way to install Intel Compiler on the Xeon Phi itself? should I even do it in case the main program should&lt;/P&gt;
&lt;P&gt;only be run on the Phi and not compiled on it?&lt;/P&gt;
&lt;P&gt;Thank you very much once again,&lt;/P&gt;
&lt;P&gt;Chen&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jul 2013 13:20:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943253#M17615</guid>
      <dc:creator>Chen_S_1</dc:creator>
      <dc:date>2013-07-07T13:20:54Z</dc:date>
    </item>
    <item>
      <title>For a), execute them all on</title>
      <link>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943254#M17616</link>
      <description>&lt;P&gt;For a), execute them all on the Intel Xeon Phi as per the first-bullet on pg. 20 under the &lt;STRONG&gt;Compiling native GNU tools&lt;/STRONG&gt; section:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;“All steps needed to build the native environment are executed on the uOS of the Intel Xeon Phi coprocessor.”&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;For b), there’s no way to install the Intel compiler on the coprocessor and no need to. It functions fine as a coprocessor cross-compiler running on the host (with &lt;STRONG&gt;-mmic&lt;/STRONG&gt;) and using the k1om binutils (distributed/installed with MPSS) to produce a complete native executable (including the main program) that can be shipped to the coprocessor and executed.&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jul 2013 14:43:51 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943254#M17616</guid>
      <dc:creator>Kevin_D_Intel</dc:creator>
      <dc:date>2013-07-07T14:43:51Z</dc:date>
    </item>
    <item>
      <title>Here are some notes that I</title>
      <link>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943255#M17617</link>
      <description>&lt;P&gt;Here are some notes that I took when compiling it a while ago. There were some strange constructs in the generated makefile that required manual fixes:&lt;/P&gt;
&lt;P&gt;Compiling for Intel M&lt;/P&gt;
&lt;P&gt;Georg&lt;/P&gt;
&lt;P&gt;Compiling for MIC:&lt;BR /&gt;========================&lt;BR /&gt;- change configure not to use stdio:&lt;BR /&gt;...&lt;BR /&gt;cat &amp;gt; $test.c &amp;lt;&amp;lt;EOF&lt;BR /&gt;extern int getchar();&lt;BR /&gt;int hello() {return 1+1;}&lt;BR /&gt;EOF&lt;BR /&gt;...&lt;BR /&gt;- prefix=`pwd`/compiled_mic CC=icc CFLAGS="-mmic -fPIC" LDSHARED="icc -shared" ./configure&lt;BR /&gt;- make; make install&lt;BR /&gt;- ignore errors about executables. They are not needed.&lt;BR /&gt;- cp compiled_mic/lib/libz.so* ../../../precompiled/lib.mic64&lt;BR /&gt;- cp compiled_mic/lib/libz.so* ../../../precompiled/lib.mic64-g&lt;/P&gt;
&lt;P&gt;Compiling fuer Intel MIC offload&lt;BR /&gt;===============================&lt;BR /&gt;$ unset TARGET_ARCH # otherwise "amd64" magically appears as a target&lt;BR /&gt;$ CC=icc CFLAGS="-offload-attribute-target=mic -fPIC" LDSHARED="icc -shared" ./configure --prefix=`pwd`/compiled_offload --64&lt;BR /&gt;$ make&lt;BR /&gt;# Creation of fat lib actually failed, because mechanism in makefile creates .o files in objcts/ and moves &lt;BR /&gt;# only the .o files are copied to .lo, not the *MIC.o files. do link step manually:&lt;BR /&gt;$ icc -shared -offload-attribute-target=mic -fPIC -D_LARGEFILE64_SOURCE=1 -o libz.so.1.2.5 adler32.o compress.o crc32.o deflate.o gzclose.o gzlib.o gzread.o gzwrite.o infback.o inffast.o inflate.o inftrees.o trees.o uncompr.o zutil.o&amp;nbsp; -lc&lt;BR /&gt;$ make test&lt;BR /&gt;$ make install&lt;BR /&gt;$ cp -d compiled_offload/lib/*.so* ../../../../3rd_party/precompiled/lib.linux64-offload&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jul 2013 09:26:09 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Anyone-compiled-zlib-for-MIC/m-p/943255#M17617</guid>
      <dc:creator>Georg_V_</dc:creator>
      <dc:date>2013-07-08T09:26:09Z</dc:date>
    </item>
  </channel>
</rss>

