Thanks Jeff - that was perfect. I grabbed the latest Intel 9.1 compiler
(9.1.049 20070320) and it works.
Anthony
On 05 Jun 2007 at 08:56:54, Jeff Squyres wrote:
> FWIW, I have seen this same problem with older versions of the Intel
> 9.1 compiler in Open MPI (and since OMPI's C++ bindings were derived
> from LAM's C++ bindings, there is probably a correlation here).
>
> There was a bug in all versions of the Intel 9.1 compiler related to
> this issue. I reported this problem to Intel; they confirmed the bug
> and then fixed it in a recent service release. I don't recall the
> exact version that fixed it, but I have the following version of the
> intel compilers and they work for me:
>
> [5:48] svbu-mpi:~ % icc --version
> icc (ICC) 9.1 20070109
> Copyright (C) 1985-2007 Intel Corporation. All rights reserved.
>
>
>
> On Jun 1, 2007, at 10:44 AM, Anthony R Fletcher wrote:
>
> > I successfully compiled the cxxhello program from the LAM examples but
> > get a run time error when I run it. Lamboot starts correctly, lamnodes
> > works as do programs compiled with mpicc.
> >
> > I'm running lam, version 7.2b1svn10376 from the SVN repository,
> > compiled
> > with the Intel compiler, version 9.1.043. I see the same thing with
> > version 7.2b1svn10366.
> >
> > The platform is a Fedora Core 6, 32-bit Athlon system,
> >
> > The error from cxxhello is
> >
> > % mpirun C ./cxxhello
> > MPI_Comm_rank: invalid communicator: Invalid argument (rank 0,
> > MPI_COMM_WORLD)
> > Rank (0, MPI_COMM_WORLD): Call stack within LAM:
> > Rank (0, MPI_COMM_WORLD): - MPI_Comm_rank()
> > Rank (0, MPI_COMM_WORLD): - main()
> > MPI_Comm_rank: invalid communicator: Invalid argument (rank 1,
> > MPI_COMM_WORLD)
> > Rank (1, MPI_COMM_WORLD): Call stack within LAM:
> > Rank (1, MPI_COMM_WORLD): Call stack within LAM:
> >
> > ----------------------------------------------------------------------
> > -------
> > One of the processes started by mpirun has exited with a nonzero
> > exit
> > code. This typically indicates that the process finished in error.
> > If your process did not finish in error, be sure to include a
> > "return
> > 0" or "exit(0)" in your C code before exiting the application.
> >
> > PID 27324 failed on node n0 (192.168.1.3) with exit status 22.
> >
> > ----------------------------------------------------------------------
> > -------
> >
> > This has worked with the version 8 Intel compiler.
> >
> > Am I missing some vital flag to icpc? Any suggestions?
> >
> > Anthony.
> >
> > --
> > Anthony R Fletcher
> > Room 2033, Building 12A, http://dcb.cit.nih.gov/~arif
> > National Institutes of Health, arif_at_[hidden]
> > 12A South Drive, Bethesda, Phone: (+1) 301 402 1741.
> > MD 20892-5624, USA.
> > <laminfo.txt>
> > _______________________________________________
> > This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
>
> --
> Jeff Squyres
> Cisco Systems
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
--
Anthony R Fletcher
Room 2033, Building 12A, http://dcb.cit.nih.gov/~arif
National Institutes of Health, arif_at_[hidden]
12A South Drive, Bethesda, Phone: (+1) 301 402 1741.
MD 20892-5624, USA.
|
