A quick reading of this thread makes it sound to me as if you are
using icc to compile c++ code. The correct compiler to use is icpc.
This has been the case since at least the version 9 release of the
Intel compilers. icc will not compile c++ code.
Hope this is useful.
-david
--
David G
On Oct 16, 2007, at 11:20 AM, Brian Granger wrote:
Wow, that is quite a study of the different options. I will spend
some time looking over things to better understand the (complex)
situation. I will also talk with Lisandro Dalcin about what he thinks
the best approach is for mpi4py.
Brian /
I just built OpenMPI-1.2.4 to work on my system (IB, OFED-1.2).
When I run a job, I am getting the following message:
WARNING: There are more than one active ports on host 'w74', but the
default subnet GID prefix was detected on more than one of these
ports. If these ports are connected to
I don't think this will be a problem. We are now setting the flags
correctly and doing a dlopen, which should enable the components to
find everything in libmpi.so. If I remember correctly this new change
would simply make all components compiled in a consistent way.
I will run this by Lisandro
On Dec 10, 2007, at 3:06 PM, Craig Tierney wrote:
I just built OpenMPI-1.2.4 to work on my system (IB, OFED-1.2).
When I run a job, I am getting the following message:
WARNING: There are more than one active ports on host 'w74', but the
default subnet GID prefix was detected on more than on
Ok. I was planning to do this for OMPI v1.3 and above; not really
planning to do this for the OMPI v1.2 series. We don't have an exact
timeframe for OMPI v1.3 yet -- best guesses at this point is that
it'll be somewhere in 1HCY08.
On Dec 10, 2007, at 5:03 PM, Brian Granger wrote:
I don
