Some Success ! code works on single processor..but lamboot failure on
remote machine and a couple of Questions:
Yes Tim, the source code names were .C, I changed it .c
1. I used the following combination
mpiCC to compile and link :: OK
mpicc to compile and mpiCC to link :: ERROR
mpicc to compile and link :: ERROR
I have put the Error Output in the attached file error-make-prmpi.
so now I am using "mpiCC"
>>make prmpi.x
But it gave the following error when I run:>>
mpirun -np 8 prmpi.x
prmpi.x: error while loading shared libraries: libcxaguard.so.5: cannot
open shared object file: No such file or directory
But after I made the following change:
Added /opt/intel_cc_80/lib, /opt/intel_fc_80/lib to /etc/ld.so.conf and run
ldconfig as root
And now I run "mpirun -np 8 prmpi.x", and it WORKS!
Any clue why it is giving trouble with "mpicc".
My serial code with "icc" compiler works fine.
The variables "nAtomType,npd,nvm" etc.. are "CONSTANTS" declared in a
params.h.
I have included params.h in all the ".c" source files, since these are
needed in all these files.
2. Another problem is running the lamboot on mutiple machines.
I have put the error output of lamboot -d lamhosts in the attached file
error-lamboot
thanks-
-sumeet-
-----Original Message-----
From: Tim Prince [mailto:tprince_at_[hidden]]
Sent: Wednesday, July 06, 2005 9:44 AM
To: kapurs_at_[hidden]
Cc: tprince_at_[hidden]; General LAM/MPI mailing list
Subject: Re: LAM: Trouble installing LAM 7.1.1 on Red Hat Linux 3 ES
Sumeet Kapur wrote:
>I am using "C" and want to use icc ?
>Doesn't lam build the mpicc (a c compiler) when I compile and install it.
>Also can you please tell me how to build a mpicc compiler if it doesn't get
>build on its own.
>
>What does it mean when you say ..
>".....not a recommended way to go. If you meant C, get rid of your C++
>stuff...."
>
>
>
Your top posting makes it difficult to reply, except by removing the
original stuff. Surely, you've noticed by now, that icc makes the same
distinction as gcc, as far as possible: it assumes that your code is C
code, unless known to be C++. So, when you use mpicc built with gcc or
icc, it doesn't link any C++ libraries by default. If you don't
know which of your code is C++, you could use nm to search the .o files
and find out which ones contain those C++ references. Did you make a
mistake in the source file name? For example, file.C, like file.cpp, is
taken as C++.
|
