Now I would like to test it with a simple hello project. Ralph Castain suggest me the following web site: https://wiki.mst.edu/nic/examples/openmpi-intel-fortran90-example
This is the results of my simulation: Hello World! I am 0 of 1 How ever I have a quad core processor, I belive (I run a cat /proc/cpuinfo) [Tom] What was your mpirun command? Did it have a '-np 4' in it to tell mpirun that you want 4 processes to be spawned? Don't be afraid to read the FAQ on running MPI programs: http://www.open-mpi.org/faq/?category=running -Tom Thanks a lot Diego On 26 November 2012 13:49, Gus Correa <g...@ldeo.columbia.edu<mailto:g...@ldeo.columbia.edu>> wrote: Hi Diego > deal all, dear Gustavo, > > This is my bash.bashrc in ubuntu 12.04: > > ############################################## > /PATH="/opt/intel/bin/compilervars.sh intel64$PATH"/ > /source /opt/intel/bin/compilervars.sh intel64/ > /source /opt/intel/mkl/bin/mklvars.sh intel64 mod lp64/ > /export PATH/ > ############################################## This is not an OpenMPI problem, but about Linux environment setup. Anyway, my guess is that all you need in your .bashrc are these two lines (2 and 3): source /opt/intel/bin/compilervars.sh intel64 source /opt/intel/mkl/bin/mklvars.sh intel64 mod lp64 The first line is probably messing up your PATH, the fourth line may be just redundant with the the Intel compilervars.sh script. Try commenting out lines 1 and 4 (with a leading # character), and leave only lines 2 and 3. (Note, no '/' in the beginning or at the end of the lines, not sure if the '/'s are part of your .bashrc or just part of your email.) After you make the change, then login again, or open a new terminal/shell window and try these commands: which icc which icpc which ifort printenv to make sure your environment is pointing to the correct Intel compilers. I hope this helps, Gus Correa On 11/26/2012 09:42 AM, Diego Avesani wrote: I think that is correct according to your mail, so I do not think that this is this problem. I check the config.log file. It says: checking for gcc ############################################## /configure:5133: result: icc/ /configure:5362: checking for C compiler version/ /configure:5371: icc --version >&5/ /./configure: line 5373: icc: command not found/ /configure:5382: $? = 127/ /configure:5371: icc -v >&5/ ############################################## When I write the simple project inside the config.log file in new file .c ############################################## int main () { ; return 0; } ############################################## it works when I compile it with icc Do I probably need to change also the .csh? My current intel version is 13.0, When I compile it they told me to set /compilervars.sh /moreover check iccvars.sh, ifortvars.sh and /compilervars.sh, /they are the same. I do not know what to do, could I compile open mpi with gcc, gcpc,gnufort and then use it with intel fortran? do you think that is a OpenMpi problem? Has someone compile it with intel linux icc? which distro have you used? Thank all Diego On 25 November 2012 22:21, Gustavo Correa <g...@ldeo.columbia.edu<mailto:g...@ldeo.columbia.edu> <mailto:g...@ldeo.columbia.edu<mailto:g...@ldeo.columbia.edu>>> wrote: urce compilervars.sh intel64 _______________________________________________ users mailing list us...@open-mpi.org<mailto:us...@open-mpi.org> http://www.open-mpi.org/mailman/listinfo.cgi/users _______________________________________________ users mailing list us...@open-mpi.org<mailto:us...@open-mpi.org> http://www.open-mpi.org/mailman/listinfo.cgi/users
