<div dir="ltr">Dear Gerhard,<div><br></div><div> An ifort version, ifort.cfg is there in intel64 directory. Whether ifort and ifort.cfg are same?...Whenever, I set the path for ifort.cfg in .bashrc_profile, and after sourcing it...ifort seems to be installed as can be checked from ifort -v command in terminal....However, when I am logging out..& log in ...ifort seems to be missing with ifort command not found in the terminal. What could be the reason?</div><div><br></div><div>Looking forward to your suggestion in this regard.</div><div><br></div><div>with regards, </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 17, 2015 at 12:43 AM, shamik chakrabarti <span dir="ltr"><<a href="mailto:shamikphy@gmail.com" target="_blank">shamikphy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Dear Gerhard,<div><br></div><div> As I have not installed the Composer_xe_2015 version to our server, I don't have any idea whether the installation of intel64 version of ifort was restricted or not, However...I can do one thing: I can install l_fcompxe_2013_sp1.1.106 to our home directory and link the path of ifort and mkl accordingly. As I have installed wien2k with this compiler previously & it contains the intel64 version of ifort, we may not face any problem. At the moment, I think this could be the solution.</div><div><br></div><div>Dear Gavin,</div><div><br></div><div> Thank you for your suggestions. Yes I will follow those links and try to gain more knowledge of installing wien2k in PHI processor...</div><div><br></div><div>Thank you once again.</div><div><br></div><div>with regards, </div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 16, 2015 at 8:47 PM, Gavin Abo <span dir="ltr"><<a href="mailto:gsabo@crimson.ua.edu" target="_blank">gsabo@crimson.ua.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Since you say that the "segmentation fault (core dumped)" error occurs during the running of ifort, you might also want to ask about the error in the Intel Fortran Compiler for Linux* and Mac OS X* forum [ <a href="https://software.intel.com/en-us/forum" rel="noreferrer" target="_blank">https://software.intel.com/en-us/forum</a> ]. One of the Intel representatives might know if it could caused by the DPD200364057 Fortran Internal Compiler Error when compiling with -openmp or one of the other bugs listed or not listed in the 2015 Composer Edition Compilers Fixes List [ <a href="https://software.intel.com/en-us/articles/intel-composer-xe-2015-compilers-fixes-list" rel="noreferrer" target="_blank">https://software.intel.com/en-us/articles/intel-composer-xe-2015-compilers-fixes-list</a> ].<div><div><br>
<br>
On 7/16/2015 8:50 AM, Fecher, Gerhard wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear Shamik,<br>
- what main processor does your computer have ? (It cannot be XEON PHI as this is a co-processor on some extra card)<br>
<br>
- if you compile for the XEON Phi, Wien2k will most probably not work on the main processor of your computer<br>
that is, if you compile it native for the PHI then you have to run it on the PHI<br>
check the Intel manuals and the Intel link advisor for the PHI off-load models and how to use the mic options.<br>
<br>
- the XEON PHIs are implemented since the 2013 versions (e.g. parallel_studio_xe_2013) and those have also the emt64 versions<br>
of ifort (in /opt/intel/composer_xe_2013.5.192/bin/intel64), icc, mkl (in /opt/intel/composer_xe_2013.5.192/mkl/lib/intel64) etc.<br>
<br>
- the composer_xe_2015_090 has both, intel_64 and intel64_mic for ifort and icc (or did you restrict the installation somehow ?)<br>
(interesting I don't have a special mic directory for the mkl of xe_2015, but may be I just didn't install it<br>
because the mic directory contains libraries only for native PHI programs)<br>
<br>
Ciao<br>
Gerhard<br>
<br>
DEEP THOUGHT in D. Adams; Hitchhikers Guide to the Galaxy:<br>
"I think the problem, to be quite honest with you,<br>
is that you have never actually known what the question is."<br>
<br>
====================================<br>
Dr. Gerhard H. Fecher<br>
Institut of Inorganic and Analytical Chemistry<br>
Johannes Gutenberg - University<br>
55099 Mainz<br>
and<br>
Max Planck Institute for Chemical Physics of Solids<br>
01187 Dresden<br>
________________________________________<br>
Von: <a href="mailto:wien-bounces@zeus.theochem.tuwien.ac.at" target="_blank">wien-bounces@zeus.theochem.tuwien.ac.at</a> [<a href="mailto:wien-bounces@zeus.theochem.tuwien.ac.at" target="_blank">wien-bounces@zeus.theochem.tuwien.ac.at</a>] im Auftrag von shamik chakrabarti [<a href="mailto:shamikphy@gmail.com" target="_blank">shamikphy@gmail.com</a>]<br>
Gesendet: Donnerstag, 16. Juli 2015 14:42<br>
An: A Mailing list for WIEN2k users<br>
Betreff: Re: [Wien] Wien2k installation problem<br>
<br>
Dear Gerhard & Gavin,<br>
<br>
The compiler ifort is available only in mic directory for composer_xe_2015.0.090, and that's why we have also set the path of mkl to mic as otherwise we are getting an error of not finding mkl libs by X86_64-K1om-linux-ld:<br>
<br>
However, after setting the path of mkl to mic, there were no such error appeared except,<br>
<br>
segmentation fault (core dumped).<br>
<br>
This error is again appeared due to ifort (& not by gcc)<br>
<br>
The appearance of error is independent of whether we have set $(FOPT) or not to Linker Flags.<br>
<br>
All the -pthread are converted to -lpthread in the OPTION<br>
<br>
However, the error segmentation fault (core dumped) is still appearing after compiling & this is the only one error we are left with.<br>
<br>
Do you think that if we use some older version of compiler in which "ifort" is available in intel64...then the problem may be solved?...<br>
<br>
However, I have no idea that whether the older version of compiler is compatible with "XEON PHI" processor?<br>
<br>
Looking forward to your suggestion in this regard.<br>
<br>
with regards,<br>
<br>
<br>
On Wed, Jul 15, 2015 at 8:49 PM, Gavin Abo <<a href="mailto:gsabo@crimson.ua.edu" target="_blank">gsabo@crimson.ua.edu</a><mailto:<a href="mailto:gsabo@crimson.ua.edu" target="_blank">gsabo@crimson.ua.edu</a>>> wrote:<br>
Dear Gerhard and Shamik,<br>
<br>
Ok, sorry, I did not think too much into it.<br>
<br>
In siteconfig,<br>
<br>
1) selected "S specify a system" and "I Linux (Intel ifort compiler (12.0 and later) + mkl )"<br>
2) selected "O specify compiler options, BLAS and LAPACK", and it gave:<br>
<br>
Recommended options for system linuxifc are:<br>
Compiler options: -FR -mp1 -w -prec_div -pc80 -pad -ip -DINTEL_VML -traceback -assume buffered_io<br>
Linker Flags: $(FOPT) -L$(MKLROOT)/lib/$(MKL_TARGET_ARCH) -pthread<br>
Preprocessor flags: '-DParallel'<br>
R_LIB (LAPACK+BLAS): -lmkl_lapack95_lp64 -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core -openmp -lpthread<br>
<br>
I knew that these recommended 64 bit settings have worked fine for me on different Linux operating systems. Until you mentioned it, I did not know that -pthread could be safely dropped from the Linker Flags.<br>
<br>
Thanks,<br>
<br>
Gavin<br>
<br>
<br>
why -pthread instead of -lpthread ? The threading library is libpthread and should be linked with -lpthread !<br>
I remembre that I made some ten years ago the remark on that: On SUSE systems (at thae time it was 9.2 and older) one can have a very comfortable setup of the linker<br>
such that it finds the standart libraries by itself. You can check it if you remove the -pthread switch from the linker line and find that Wien2k is still linked correctly.<br>
If not then you may use ldconfig to make your linker environment more comfortable.<br>
<br>
<br>
Below I do not understand why the linker should need the compiler options (LDFLAGS:$(FOPT)) ??<br>
<br>
_______________________________________________<br>
Wien mailing list<br>
<a href="mailto:Wien@zeus.theochem.tuwien.ac.at" target="_blank">Wien@zeus.theochem.tuwien.ac.at</a><mailto:<a href="mailto:Wien@zeus.theochem.tuwien.ac.at" target="_blank">Wien@zeus.theochem.tuwien.ac.at</a>><br>
<a href="http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien" rel="noreferrer" target="_blank">http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien</a><br>
SEARCH the MAILING-LIST at: <a href="http://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/index.html" rel="noreferrer" target="_blank">http://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/index.html</a><br>
<br>
<br>
<br>
<br>
--<br>
Shamik Chakrabarti<br>
Senior Research Fellow<br>
Dept. of Physics & Meteorology<br>
Material Processing & Solid State Ionics Lab<br>
IIT Kharagpur<br>
Kharagpur 721302<br>
INDIA<br>
</blockquote>
_______________________________________________<br>
Wien mailing list<br>
<a href="mailto:Wien@zeus.theochem.tuwien.ac.at" target="_blank">Wien@zeus.theochem.tuwien.ac.at</a><br>
<a href="http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien" rel="noreferrer" target="_blank">http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien</a><br>
SEARCH the MAILING-LIST at: <a href="http://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/index.html" rel="noreferrer" target="_blank">http://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/index.html</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Shamik Chakrabarti<br>Senior Research Fellow<br>Dept. of Physics & Meteorology<br>Material Processing & Solid State Ionics Lab<br>IIT Kharagpur<br>Kharagpur 721302<br>INDIA</div>
</div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Shamik Chakrabarti<br>Senior Research Fellow<br>Dept. of Physics & Meteorology<br>Material Processing & Solid State Ionics Lab<br>IIT Kharagpur<br>Kharagpur 721302<br>INDIA</div>
</div>