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 [
https://en.wikipedia.org/wiki/Static_build ]. 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" [
Of note, the Intel link advisor [
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".
On 12/27/2015 12:19 AM, Dr. K. C. Bhamu wrote:
Thank you Dr. Gavin.
It means if we dont no the path of compiles and libraries it detects
automatic. Am I right?
On Sat, Dec 26, 2015 at 9:36 PM, Gavin Abo <gs...@crimson.ua.edu
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).
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).
On 12/25/2015 10:24 AM, Dr. K. C. Bhamu wrote:
Dear Prb Blaha
What is the difference between Wien2k tar file and wien2k
Wien mailing list
SEARCH the MAILING-LIST at: