Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have recently purchased a workstation (hp xw9300) which is pretty good:
2X Dual core AMD Opteron 285 2.6GHz, 1MB cache
2X 300 GB U320 SCSI 10.000 rpm
In short it is a 2-processor, dual core machine with a total of 600GB memory. (It acts like 4 porocessors.) I have RHEL 4.0 installed on the workstation.
It is a high spec because I use it for scientific work; in particular I compile and run large codes written in FORTRAN, with applications to fluid mechanics type problems -- that means large grid sizes, hence the need for very large memory.
My question relates to fortran compilers. The machine comes installed with with the g77 compiler, which is the standard fortran77 (f77) compiler and that works very nicely and there is no problem.
It also comes witht the gfortran compiler which is the fortran95 (f95) compiler which is slowly replacing f77. I was delighted, but then found much to my annoyance that codes that I rewote in f95 and compiled with gfortran were slower than the f77 version! So I had to go back to the old version.
I have tried to find a suitable f95 compiler for RHEL, but I have been unable to -- there is no official version as far as I can see except for gfortran.
So, my basic question is, can any one help and find a fast f95 compiler suitable for RHEL for me? Are there forums where I can look out for it?
Click Accept, then scroll down to Compilers, and click on
# Intel® C++ Compiler Professional Edition for Linux*
You then have to register with them to get the download link, if memory serves. Then you just download the tarball, and install it. Can't remember exactly what the install procedure is, but it's not rocket science.
Click Accept, then scroll down to Compilers, and click on
# Intel® C++ Compiler Professional Edition for Linux*
You then have to register with them to get the download link, if memory serves. Then you just download the tarball, and install it. Can't remember exactly what the install procedure is, but it's not rocket science.
Great -- I have installed the Intel64 fortran compiler successfully. Thanks!
Just a couple of niggly bits:
(1) The instalation guide mentions how to set ip the Compiler Environment
The programs in the Intel Fortran Compiler 10.0 for Linux product rely on the environment variables PATH and LD_LIBRARY_PATH. The installation script (install.sh) creates compiler environment script files (ifortvars.sh/idbvars.sh) that set these variables. It is strongly recommended that you add those script files into your login script (.login file). Once the variables are set in the ".login" file there is no need to run the script files for each session.
source the script to setup the compiler environment:
* > source <install-dir>/bin/ifortvars.sh(.csh)
to use ifort
* > source <idb-install-dir>/bin/idbvars.sh(.csh)
to use idb
However, I cannot find '.login' file in my root directory; but I have the usual files like .bashrc and /etc/login.d and so on. So which is my real login script file where I should add the variables?
The script files are /opt/intel/fce/10.0.023/bin/ifortvars.sh(.csh) Should I add the entire contents of both of these files to the end of my login script file? Or is it enough just to add,
> source /opt/intel/fce/10.0.023/bin/ifortvars.sh
to my login script? (By the way what is the difference between the *.sh and *.csh files?)
(2) If I can be allowed to sneak in an 'ifort' question (its a quicky). With the g77 compiler I use the options: > g77 -Wall -ffast-math -funroll-all-loops -funroll-loops -O3 ......
Does any one know what the best options with the ifort compiler in order to maximmise the speed of vectorising, loop unrollingm i.e. make the executible as fast as possible?
"However, I cannot find '.login' file in my root directory; but I have the usual files like .bashrc and /etc/login.d and so on. So which is my real login script file where I should add the variables?"
Different distributions use different files for login defaults. The files in the root directory are universal defaults which apply to all users. The files appended to user directories apply only to that user. If your distribution uses .bashrc then /home/user/.bashrc contains the local defaults and somewhere in /etc you will find a .bashrc which contains the universal defaults.
"By the way what is the difference between the *.sh and *.csh files?"
You can have several different shells like bash, ksh, etc. .sh is a symbolic link to whichever shell you are using as the default shell. csh is the c shell.
If your distribution uses .bashrc then /home/user/.bashrc contains the local defaults and somewhere in /etc you will find a .bashrc which contains the universal defaults.
-----------------
Steve Stites
Thanks jailbait. I am using RHEL 4.0 WS. I will put the script into my root /etc/bashrc file since I want all users to be able to access ifort.
So, do I just add the following line at the end of /etc/baschrc :
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.