<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I believe the __libm_sse2_sincos symbol is defined in the files
called libimf.a or libimf.so. If the Intel Fortran compiler is
installed in the default location, then both of those files are
usually in the /opt/intel/lib/intel64 directory on a 64 bit system.
Do those two files exist on your system?</p>
<p>The compilervars.sh script usually has to be executed so that the
Linux environment can find those files. Did you have a source
line for compilervars.sh in your .bashrc? If not, refer the Intel
documentation at the following two links:</p>
<a class="moz-txt-link-freetext" href="https://software.intel.com/en-us/intel-system-studio-cplusplus-compiler-18.0-user-and-reference-guide-using-compilervars-file">https://software.intel.com/en-us/intel-system-studio-cplusplus-compiler-18.0-user-and-reference-guide-using-compilervars-file</a><br>
<a class="moz-txt-link-freetext" href="https://software.intel.com/en-us/articles/setting-up-the-build-environment-for-using-intel-c-or-fortran-compilers">https://software.intel.com/en-us/articles/setting-up-the-build-environment-for-using-intel-c-or-fortran-compilers</a><br>
<br>
Also, you can check the mailing list archive [
<a class="moz-txt-link-freetext" href="https://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/maillist.html">https://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/maillist.html</a>
] for examples like:<br>
<br>
source <font color="#666666">replace_this_with_the_path_to_your_ifort_installation</font>/compilervars.sh
intel64<br>
<br>
source /opt/intel/bin/compilervars.sh intel64 [
<a class="moz-txt-link-freetext" href="https://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/msg16702.html">https://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/msg16702.html</a>
]<br>
<br>
source
/opt/ud/intel_xe_2016/parallel_studio_xe_2016.3.067/compilers_and_libraries_2016/linux/bin/compilervars.sh
intel64 [
<a class="moz-txt-link-freetext" href="https://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/msg16590.html">https://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/msg16590.html</a>
]<br>
<br>
Though, on a cluster, you may want to first talk with your
administrator before doing that, because it may be that they have
some other procedure to set the environment for a WIEN2k calculation
like a module load [
<a class="moz-txt-link-freetext" href="https://wiki.cse.ucdavis.edu/support/hpc/software/wien2k">https://wiki.cse.ucdavis.edu/support/hpc/software/wien2k</a> ].<br>
<br>
<div class="moz-cite-prefix">On 6/6/2018 9:07 AM, venkatesh
chandragiri wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACS+pXMzig-OnQr0LpKoLfRRO4771uJZOc931k27TY99s9NrkA@mail.gmail.com">
<div dir="ltr">
<div>Dear wien2k users,</div>
<div><br>
</div>
<div>I have successfully complied Wine2k_16 and start to run
init_lapw for the MnSb compound. Up to kgen it was
successfully done. But for dstart it shows error as given
below. </div>
<div><br>
</div>
<div>===================================================<br>
</div>
<div> next is dstart<br>
> dstart -c -p (22:46:57) running dstart in single
mode<br>
dstart: symbol lookup error: dstart: <b>undefined symbol:
__libm_sse2_sincos</b><br>
0.015u 0.009s 0:00.06 16.6% 0+0k 0+0io 0pf+0w<br>
error: command /share/home/venky/soft/wien2k/dstartpara -c
dstart.def failed<br>
n stop error n<br>
[venky@mgt02 MnSb]$ x dstart<br>
/share/home/venky/soft/wien2k/dstart: <b>symbol lookup error:
</b>/share/home/venky/soft/wien2k/dstart: <b>undefined
symbol: __libm_sse2_sincos</b><br>
0.002u 0.002s 0:00.00 0.0% 0+0k 0+0io 0pf+0w<br>
error: command /share/home/venky/soft/wien2k/dstart
dstart.def failed</div>
<div><br>
</div>
<div>========================</div>
<div><br>
</div>
<div>This problem was not seen the wien2k_13 which was installed
in the other server previously. kindly guide me to rectify
this error.</div>
<div><br>
</div>
<div>thanks </div>
<div><br>
</div>
<div>venkatesh<br>
</div>
</div>
</blockquote>
</body>
</html>