<?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 Lapack undefined symbols in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Lapack-undefined-symbols/m-p/764877#M178</link>
    <description>That's a good point. USE lapack95 and mkl95_lapack should work interchangeably in this case.</description>
    <pubDate>Fri, 26 Aug 2011 18:26:25 GMT</pubDate>
    <dc:creator>TimP</dc:creator>
    <dc:date>2011-08-26T18:26:25Z</dc:date>
    <item>
      <title>Lapack undefined symbols</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Lapack-undefined-symbols/m-p/764874#M175</link>
      <description>Im running ifort 12.0 with command:&lt;DIV&gt;&lt;DIV id="_mcePaste"&gt;ifort -r8 main.f90 -lmkl_core -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_lapack95_lp64&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;and all is ok with a fortran95 call to the lapack routine gesv. However, if I replace gesv by calls to getrf and getri, it tells me these are "Undefined symbols". Why does it recognise gesv but not getrf or getri?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 26 Aug 2011 15:31:47 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Lapack-undefined-symbols/m-p/764874#M175</guid>
      <dc:creator>scriabin3</dc:creator>
      <dc:date>2011-08-26T15:31:47Z</dc:date>
    </item>
    <item>
      <title>Lapack undefined symbols</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Lapack-undefined-symbols/m-p/764875#M176</link>
      <description>Do you have the 
USE mkl95_lapack 
at the top of the calling subroutine?  It should result in getrf and getri being translated to other functions, eventually down to the f77 ?getrf and ?getri which are provided in libmkl_lapack95_lp64.
You may need to assure that you have the include path (-I) for the mkl/include/lp64 in your installation.</description>
      <pubDate>Fri, 26 Aug 2011 16:06:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Lapack-undefined-symbols/m-p/764875#M176</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2011-08-26T16:06:35Z</dc:date>
    </item>
    <item>
      <title>Lapack undefined symbols</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Lapack-undefined-symbols/m-p/764876#M177</link>
      <description>Oh dear, it's an old code, so I only just noticed it has at the top "use lapack95, only: gesv", how embarrassing... In any case, is there a difference between "use lapack95" and "usemkl95_lapac"?</description>
      <pubDate>Fri, 26 Aug 2011 16:35:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Lapack-undefined-symbols/m-p/764876#M177</guid>
      <dc:creator>scriabin3</dc:creator>
      <dc:date>2011-08-26T16:35:30Z</dc:date>
    </item>
    <item>
      <title>Lapack undefined symbols</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Lapack-undefined-symbols/m-p/764877#M178</link>
      <description>That's a good point. USE lapack95 and mkl95_lapack should work interchangeably in this case.</description>
      <pubDate>Fri, 26 Aug 2011 18:26:25 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Lapack-undefined-symbols/m-p/764877#M178</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2011-08-26T18:26:25Z</dc:date>
    </item>
  </channel>
</rss>

