<?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 Possibilty to keep using PSXE 2016 intel Fortran compiler in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273204#M8075</link>
    <description>&lt;P&gt;Hello Intel Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;is it possible to keep using the 2016 intel Fortran compiler, maybe in combination with an oneAPI license? I would need the 2016 version as it is the last one supported by an external user subroutine linked with Abaqus. Newer versions (including version 2021 included in oneAPI) are not compatible with the Abaqus internal runtime libraries and lead to a Abaqus runtime symbol lookup error after the succesful compilation and linking of the subroutines.&lt;/P&gt;
&lt;P&gt;Thank you very much in advance!&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;
&lt;P&gt;Jakob&lt;/P&gt;</description>
    <pubDate>Tue, 13 Apr 2021 12:03:36 GMT</pubDate>
    <dc:creator>JHWKM</dc:creator>
    <dc:date>2021-04-13T12:03:36Z</dc:date>
    <item>
      <title>Possibilty to keep using PSXE 2016 intel Fortran compiler</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273204#M8075</link>
      <description>&lt;P&gt;Hello Intel Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;is it possible to keep using the 2016 intel Fortran compiler, maybe in combination with an oneAPI license? I would need the 2016 version as it is the last one supported by an external user subroutine linked with Abaqus. Newer versions (including version 2021 included in oneAPI) are not compatible with the Abaqus internal runtime libraries and lead to a Abaqus runtime symbol lookup error after the succesful compilation and linking of the subroutines.&lt;/P&gt;
&lt;P&gt;Thank you very much in advance!&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;
&lt;P&gt;Jakob&lt;/P&gt;</description>
      <pubDate>Tue, 13 Apr 2021 12:03:36 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273204#M8075</guid>
      <dc:creator>JHWKM</dc:creator>
      <dc:date>2021-04-13T12:03:36Z</dc:date>
    </item>
    <item>
      <title>Re: Possibilty to keep using PSXE 2016 intel Fortran compiler</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273247#M8077</link>
      <description>&lt;P&gt;This is a known bug with a known workaround.&amp;nbsp; Use /names:lowercase along with /iface:cref.&lt;/P&gt;
&lt;P&gt;Read all about it &lt;A href="https://community.intel.com/t5/Intel-Fortran-Compiler/Abaqus-others-names-not-lowercase-iface-cref-bug-Win-v2021-1-x/m-p/1273245/thread-id/155492" target="_self"&gt;HERE&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Apr 2021 15:03:59 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273247#M8077</guid>
      <dc:creator>Ron_Green</dc:creator>
      <dc:date>2021-04-13T15:03:59Z</dc:date>
    </item>
    <item>
      <title>Re:Possibilty to keep using PSXE 2016 intel Fortran compiler</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273250#M8078</link>
      <description>&lt;P&gt;We have not changed our Fortran ABI and APIs for many many many years.  The latest compilers should work with 3rd party programs EVEN IF they don't list the latest compiler under their Requirements or Support documentation.  Our advice is try the new compiler and we're sure it will work.  If not it's a bug and we'll fix it.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Apr 2021 15:19:38 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273250#M8078</guid>
      <dc:creator>Ron_Green</dc:creator>
      <dc:date>2021-04-13T15:19:38Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Possibilty to keep using PSXE 2016 intel Fortran compiler</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273255#M8080</link>
      <description>&lt;P&gt;Hi Ronald,&lt;/P&gt;
&lt;P&gt;thank you for the fast reply!&lt;/P&gt;
&lt;P&gt;However I am not using windows but a ubuntu 18 instead. So this bug should actually not appear in my case as far as I understood. Abaqus actually finishes compiling and linking succesfully and starts the Abaqus executable but fails immediatly at runtime with the symbol look up error: 'undefined symbol __for_ieee_quiet_ne_k8_ '&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;/P&gt;
&lt;P&gt;Jakob&lt;/P&gt;</description>
      <pubDate>Tue, 13 Apr 2021 15:33:11 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273255#M8080</guid>
      <dc:creator>JHWKM</dc:creator>
      <dc:date>2021-04-13T15:33:11Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Possibilty to keep using PSXE 2016 intel Fortran compiler</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273350#M8082</link>
      <description>&lt;P&gt;something is wrong in your environment.&amp;nbsp; that function is in libifcore, which is in /opt/intel/oneapi/compiler/2021.2.0/linux/compiler/lib/intel64.&amp;nbsp; Do you have that path in your LD_LIBRARY_PATH?&lt;/P&gt;
&lt;P&gt;or&lt;/P&gt;
&lt;P&gt;/opt/intel/oneapi/compiler/latest/linux/compiler/lib/intel64&lt;/P&gt;
&lt;P&gt;Did you&lt;/P&gt;
&lt;P&gt;source /opt/intel/oneapi/setvars.sh&lt;/P&gt;
&lt;P&gt;before starting Abaqus?&amp;nbsp; Perhaps put that in your .bashrc or other startup dot file.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Apr 2021 23:27:22 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273350#M8082</guid>
      <dc:creator>Ron_Green</dc:creator>
      <dc:date>2021-04-13T23:27:22Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Possibilty to keep using PSXE 2016 intel Fortran compiler</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273558#M8091</link>
      <description>&lt;P&gt;Hi Ronald,&lt;/P&gt;
&lt;P&gt;I sourced the /opt/intel/oneapi/setvars.sh and added it to my .bashrc file. Also checked the LD_LIBRARY_PATH and the path to the libifcore library should be included.&lt;/P&gt;
&lt;P&gt;in my filesystem the libifcore library is both in&lt;/P&gt;
&lt;P&gt;/opt/intel/oneapi/compiler/2021.1.1/linux/compiler/lib/intel64_lin&amp;nbsp; and&lt;/P&gt;
&lt;P&gt;/opt/intel/oneapi/compiler/latest/linux/compiler/lib/intel64&lt;/P&gt;
&lt;P&gt;Could this be an Abaqus internal problem? The look up error apparently happens in a .so library generated temporally for the specific Abaqus simulation job:&lt;/P&gt;
&lt;P&gt;/opt/abaqus/2018/SimulationServices/V6R2018x/linux_a64/code/bin/standard: symbol lookup error: /tmp/jhuber-037e4e68_Job-1_9860/libstandardU.so: undefined symbol: __for_ieee_quiet_ne_k8_&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;
&lt;P&gt;Jakob&lt;/P&gt;</description>
      <pubDate>Wed, 14 Apr 2021 15:49:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273558#M8091</guid>
      <dc:creator>JHWKM</dc:creator>
      <dc:date>2021-04-14T15:49:03Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Possibilty to keep using PSXE 2016 intel Fortran compiler</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273710#M8094</link>
      <description>&lt;P&gt;Its possible Abaqus hard-coded the LD_LIBRARY_PATH paths to the PSXE runtime libs or assumed the Redistributable Libraries were installed - which we are CURRENTLY not doing in oneAPI.&amp;nbsp; We're reviewing this based on feedback from this Forum.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;So try this whilst we work on the issue :&amp;nbsp; Install the oneAPI runtime for Linux&lt;/P&gt;
&lt;P&gt;&lt;A href="https://registrationcenter-download.intel.com/akdlm/irc_nas/17756/l_fortran-compiler_p_2021.2.0.136_offline.sh" target="_blank"&gt;https://registrationcenter-download.intel.com/akdlm/irc_nas/17756/l_fortran-compiler_p_2021.2.0.136_offline.sh&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;now if this does NOT work, try installing Parallel Studio XE 2020, or 2019 or any version really.&amp;nbsp; It's possible Abaqus has hard-coded a path for the older PSXE products.&amp;nbsp; And check with them if they have suggestions for fixing this issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 04:16:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273710#M8094</guid>
      <dc:creator>Ron_Green</dc:creator>
      <dc:date>2021-04-15T04:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Possibilty to keep using PSXE 2016 intel Fortran compiler</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273803#M8100</link>
      <description>&lt;P&gt;Hi Ronald,&lt;/P&gt;
&lt;P&gt;thank you for your advices.&lt;/P&gt;
&lt;P&gt;Do I have to do anything further or is the installation of the oneAPI runtime enough? Is it the same compiler I got when downloading the oneAPI HPC toolkit?&lt;/P&gt;
&lt;P&gt;Unfortunately my license for PSCXE expired so I cant test the 2020 or any of the earlier versions.&lt;/P&gt;
&lt;P&gt;I will get in touch with Abaqus about that issue.&lt;/P&gt;
&lt;P&gt;Best regards&lt;/P&gt;
&lt;P&gt;Jakob&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 10:51:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1273803#M8100</guid>
      <dc:creator>JHWKM</dc:creator>
      <dc:date>2021-04-15T10:51:30Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Possibilty to keep using PSXE 2016 intel Fortran compiler</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1274741#M8120</link>
      <description>&lt;P&gt;Jakob, I will check your older license.&amp;nbsp; I'll be in touch in direct email, we'll get you going with PSXE 2020 shortly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ron&lt;/P&gt;</description>
      <pubDate>Mon, 19 Apr 2021 15:07:49 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/Possibilty-to-keep-using-PSXE-2016-intel-Fortran-compiler/m-p/1274741#M8120</guid>
      <dc:creator>Ron_Green</dc:creator>
      <dc:date>2021-04-19T15:07:49Z</dc:date>
    </item>
  </channel>
</rss>

