In terms of compiling and installing, it all looks good that the TM
boot module was installed properly.
So the question is: why isn't it available at run-time?
Question: are you invoking lamboot in a PBS (Torque) job? The TM boot
module will only work when you launch lamboot from *inside* a PBS
(Torque) job.
On Nov 11, 2004, at 4:32 PM, Konstantin Skaburskas wrote:
> Hi,
>
> First, I compiled, installed Torque 1.1.0p4 to /usr/local, configured
> and run server and mom. Then configured LAM 7.1.1 with
>
> CC=icc
> CXX=icc
> FC=ifort
> export CC CXX FC
> ../lam-7.1.1/configure \
> --prefix=/usr/local/lam-7.1.1_intel_tm \
> --with-trillium \
> --with-prefix-memcpy \
> --with-debug \
> --with-tv-debug \
> --enable-tv-dll-force \
> --enable-shared \
> --with-purify \
> --with-rsh="ssh -x" \
> --with-boot-tm=/usr/local
>
> After LAM compilation it seems that TM module was compiled and got
> into static and shared libs (I can see ssi_boot_tm*.o in
> share/ssi/boot/tm/src/, /lam/install/dir/lib/liblam.a and 'nm' gives
> 'T' and 'D' for lam_ssi_boot_tm* and tm_* in liblam.so). However, when
> I try to run lamboot with TM module I get:
>
>> lamboot -d -ssi boot tm
> n-1<28345> ssi:boot:open: opening
> n-1<28345> ssi:boot:open: looking for boot module named tm
> n-1<28345> ssi:boot:open: opening boot module tm
> n-1<28345> ssi:boot:open: opened boot module tm
> n-1<28345> ssi:boot:select: initializing boot module tm
> n-1<28345> ssi:boot:tm: not running under PBS
> n-1<28345> ssi:boot:select: boot module not available: tm
> n-1<28345> ssi:boot:select: no boot moduless available!
> -----------------------------------------------------------------------
> ------
> No SSI boot modules said that they were available to run. This should
> not happen.
> -----------------------------------------------------------------------
> ------
>
> Simply booting the LAM gives:
>> lamboot -v
> LAM 7.1.1/MPI 2 C++/ROMIO - Indiana University
>
> n-1<28375> ssi:boot:base:linear: booting n0 (localhost)
> n-1<28375> ssi:boot:base:linear: finished
>
> I attach the output from configure, and the top-level config.log.
> laminfo gives:
> LAM/MPI: 7.1.1
> Prefix: /usr/local/lam-7.1.1_intel_tm
> Architecture: i686-pc-linux-gnu
> Configured by: konstan
> Configured on: Thu Nov 11 16:15:09 EET 2004
> Configure host: ks.ce.ut.ee
> Memory manager: ptmalloc2
> C bindings: yes
> C++ bindings: yes
> Fortran bindings: yes
> C compiler: icc
> C++ compiler: icc
> Fortran compiler: ifort
> Fortran symbols: underscore
> C profiling: yes
> C++ profiling: yes
> Fortran profiling: yes
> C++ exceptions: no
> Thread support: yes
> ROMIO support: yes
> IMPI support: no
> Debug support: yes
> Purify clean: yes
> SSI boot: globus (API v1.1, Module v0.6)
> SSI boot: rsh (API v1.1, Module v1.1)
> SSI boot: slurm (API v1.1, Module v1.0)
> SSI boot: tm (API v1.1, Module v1.1)
> SSI coll: lam_basic (API v1.1, Module v7.1)
> SSI coll: shmem (API v1.1, Module v1.0)
> SSI coll: smp (API v1.1, Module v1.2)
> SSI rpi: crtcp (API v1.1, Module v1.1)
> SSI rpi: lamd (API v1.0, Module v7.1)
> SSI rpi: sysv (API v1.0, Module v7.1)
> SSI rpi: tcp (API v1.0, Module v7.1)
> SSI rpi: usysv (API v1.0, Module v7.1)
> SSI cr: self (API v1.0, Module v1.0)
>
> Thank you in advance,
> Konstantin
>
> <conf.tar.gz>_______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
