<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Not really. If the executables are
used, the path of the compilers, which are usually set by you in
.bashrc, for Linux environment should not be needed. Therefore,
they are not detected. Regarding the libraries, it depends on
whether the executables were built by the compiler statically or
dynamically. I don't remember, but I believe the package with the
executables was built statically. If the executables were built
statically, the libraries do not have to be detected as they are
built directly into the executables [
<a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/Static_build">https://en.wikipedia.org/wiki/Static_build</a> ]. If the executables
were built dynamically, the Linux environment usually detects the
Linux libraries automatically as long as the packages for the
libraries are installed, but the path for the Fortran libraries
usually has to be set manually (in .bashrc). If the libraries are
not installed or it cannot find the libraries in the PATH, you can
get errors like "error while loading shared libraries" [
<a class="moz-txt-link-freetext" href="http://www.mail-archive.com/wien%40zeus.theochem.tuwien.ac.at/msg11434.html">http://www.mail-archive.com/wien%40zeus.theochem.tuwien.ac.at/msg11434.html</a>
].<br>
<br>
Of note, the Intel link advisor [
<a class="moz-txt-link-freetext" href="https://software.intel.com/en-us/articles/intel-mkl-link-line-advisor">https://software.intel.com/en-us/articles/intel-mkl-link-line-advisor</a>
] can generate a set of compiler settings for a static or dynamic
build by selecting the corresponding item in the drop-down list
for "Select dynamic or static linking".<br>
<br>
On 12/27/2015 12:19 AM, Dr. K. C. Bhamu wrote:<br>
</div>
<blockquote
cite="mid:CAJYci+QxOfSsRsUBqJyU8Nu_Mm+gU6Jux+R-HxEKOgB=XMa_yw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>Thank you Dr. Gavin.<br>
</div>
It means if we dont no the path of compiles and libraries it
detects automatic. Am I right?<br>
<br>
</div>
Sincerely<br>
</div>
Bhamu<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Dec 26, 2015 at 9:36 PM,
Gavin Abo <span dir="ltr"><<a moz-do-not-send="true"
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">The
first one, the tar package, contains the source code, but
it has no executable files. The source code can be
compiled to create executable files (32 bit or 64 bit).<br>
<br>
The second one, the executable package, contains the
executable files (only 64 bit), but it has no source
code. The executable files can be used by some users that
are not able to compile WIEN2k (for reasons such as they
don't have the compilers or don't know how to use a
compiler).<br>
<br>
On 12/25/2015 10:24 AM, Dr. K. C. Bhamu wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear Prb Blaha<br>
<br>
What is the difference between Wien2k tar file and
wien2k executable file?<br>
<br>
Sincerely<br>
<br>
Bhamu<br>
</blockquote>
</blockquote>
</div>
</div>
</div>
</blockquote>
</body>
</html>