On 11/29/2010 11:31 AM, Gus Correa wrote:
Hi Mauricio

Check if you have icc (in the Intel compiler bin directory/subdirectories).

Check also if it is in your PATH environment variable.
"which icc" will tell.
If not, add it to PATH.

Actually, the right way to do it
is to run the Intel scripts to set the whole compiler environment,
not only PATH.
The scripts should be called something like iccvars.csh iccvars.sh for C/C++ and ifortvars.csh ifortvars.sh for Fortran, and are also in the Intel bin directory.

You can source these scripts in your .cshrc/.bashrc file,
using the correct shell (.sh if you use [ba]sh, .csh if you use [t]csh).
This is in the Intel compiler documentation, take a look.
For the icc version mentioned, there is a compilervars.[c]sh which takes care of both C++ and Fortran (if present), as do either of the iccvars or ifortvars, when the compilers are installed in the same directory.

Also, you can compile OpenMPI with gcc,g++ and gfortran, if you want.
If they are not yet installed in your Ubuntu, you can get them with apt-get, or whatever Ubuntu uses to get packages.

icc ought to work interchangeably with gcc, provided the same g++ version is always on PATH. icc doesn't work without the g++. Thus, it is entirely reasonable to build openmpi with gcc and use either gcc or icc to build the application. gfortran and ifort, however, involve incompatible run-time libraries, and the openmpi fortran libraries won't be interchangeable.

You must take care not to mix 32- and 64-bit compilers/libraries. Normally you would build everything 64-bit, both openmpi and the application. Ubuntu doesn't follow the standard scheme for location of 32-bit vs. 64-bit compilers and libraries, but the Intel compiler version you mentioned should resolve this automatically.

--
Tim Prince

Reply via email to