Mike Roberts wrote:
> I have been trying to look into your suggestion of checking whether I
> am using LAM's mpirun.
> When I type which mpirun I get:
> /usr/bin/mpirun
> It sounded like I should get something that mentions LAM
You mentioned you used an SGI Altix... with which Unix distribution? If
it's an RPM-based one, you could discover which mpirun arre you using with
rpm -q -f /usr/bin/mpirun
Another way to discover would be with
mpirun -h 2>&1 | head -6
or simply
mpirun -h
and then double check if it says "LAM/MPI" at line 6. This is my output:
> $ mpirun -h 2>&1 | head -6
> -----------------------------------------------------------------------------
> Synopsis: mpirun [options] <app>
> mpirun [options] <where> <program> [<prog args>]
>
> Description: Start an MPI application in LAM/MPI.
Mike wrote:
> Perhaps I will send a message to the techs at the supercomputer I am
> trying to run this on. I sent them one before I posted on this forum,
> but they do not know much about OCTAVE. If you could give me some
> pointer as to what I could tell them to check, that would be very helpful.
They should check whether /usr/bin/mpirun is indeed LAM/MPI. I bet it's not.
Brian wrote:
> [...] there appears to be some installation problems tripping you up.
I agree.
Mike wrote:
> My Unix background is not that great sometimes. I was using ' instead
> of ` in the ls `laminfo ... command.
> Now when I run the command it only shows .a files and no .so files.
> Perhaps this explains everything. I will have LAM recompiled to
> enable sharing and then we will see.
I guess you were trying the following
> ls `laminfo -path libdir | cut -d: -f2`
command suggested in the mpitb web. You have had Brian confused about
"laminfo not working" :-)
Even if you manage to compile LAM for dynamic (shared) libraries, even
though you have a system where mpirun is not LAM mpirun, and the
libmpi.so loaded when mpitb-provided "MPI_Init.oct" loads is not LAM/MPI's.
You must configure your account so that you use a dynamically compiled
LAM installation in order to use mpitb. If you have a willing-to-help
sysadmin available, you are blessed: ask him for help! :-)
For instance, can you get this output in your system?
> $ ldd `which mpirun`
> linux-gate.so.1 => (0x008d0000)
> liblam.so.0 => /home/javier/lam-7.1.3/lib/liblam.so.0 (0x00a0e000)
> libdl.so.2 => /lib/libdl.so.2 (0x004d1000)
> libutil.so.1 => /lib/libutil.so.1 (0x00505000)
> libpthread.so.0 => /lib/libpthread.so.0 (0x004d7000)
> libc.so.6 => /lib/libc.so.6 (0x00369000)
> /lib/ld-linux.so.2 (0x0034c000)
This shows that my account is configured such that mpirun will load
liblam.so. If you can't get that, you can't use MPITB. If you can't get
the "mpirun -h" command to clearly state "LAM/MPI", you are not using
LAM/MPI... well, unless your mpirun is OMPI mpirun :-)
-javier
|
