Note: In fact I helped a friend who installed ifort on hardy 64bit, and there is a subtlety with respect to the procedure given by menus:
- You must first install the package libstdc + +5 before attempting to install ifort.
- Then we must create in / usr/lib32 symlink to the library libstdc + +. So.5 installed in / usr / lib:
Code:
sudo ln-s / usr / lib / libstdc + +. / usr/lib32/libstdc + +
- And finally you can install ifort.
In fact I was mostly a question about what you add in your ~ /. Bashrc, because intuition I just added this:
Code:
# Intel Fortran export PATH = / opt/intel/Compiler/bin/ia32: $ PATH
And I can compile my sources. So I have no problem, but out of curiosity I wonder what are the lines beginning with "source" and also your line:
Code:
PATH = $ PATH: / opt/intel/Compiler/bin /
Because there is no executable in the directory /opt/intel/Compiler/bin / and result I do not see the point to add it to PATH ... (I'm relatively novice, so I do not see the subtleties ...) Besides, when I put your lines in my ~ /. Bashrc and then I run a terminal.
Code:
Source / Source opt/intel/Compiler/bin/ia32/ifortvars.sh ia32 opt/intel/Compiler/bin/ia32/idbvars.sh
File extensions for source files :
With the Intel Fortran compiler can be different Fortran language standard versions to compile programs. The Fortran type is determined by the file extension of the source file, usually defined. Extension Fortran version. For FORTRAN 77 (fixed-line format). F90. I90 Fortran 90/95 (open line format). FOR FTN Fpp FORTRAN 77 (fixed line format) with preprocessing. F90 Fortran 90/95 (open-line format) with Preprocessing
Application :
In the setup is similar to the Intel Fortran compiler the GNU Fortran compiler. The most obvious differences are:
- The Intel Fortran compiler software is using ifort started
- The Intel Fortran compiler software knows the file extensions . f95 and . F95 not
- The Intel Fortran compiler software contains its own.
Bookmarks