Hi Martin,
Yeah, we appear to have some mistakes in the configuration macros. I
will correct them, but they really should not be effecting things in
this instance.
Whether Open MPI expects a 32 bit or 64 bit library depends on the
compiler. If your compiler generates 64 bit executables by default,
we will by default compile Open MPI in 64 bit mode and expect 64 bit
libraries.
Unfortunately there is no single simple flag to switch between 64 bit
and 32 bit mode. With gcc I use the follow configure line to compile
in 32 bit mode:
./configure FCFLAGS=-m32 FFLAGS=-m32 CFLAGS=-m32 CXXFLAGS=-m32 --with-
wrapper-cflags=-m32 --with-wrapper-cxxflags=-m32 --with-wrapper-
fflags=-m32 --with-wrapper-fcflags=-m32
I know that is a bit unwieldy, but I believe that is the best way to
do it right now.
If this does not work, please send the information requested here:
http://www.open-mpi.org/community/help/
Thanks,
Tim
On Oct 19, 2006, at 2:48 PM, Audet, Martin wrote:
Hi,
When I tried to install OpenMPI on the front node of a cluster
using OpenPBS batch system (e.g. --with-tm=/usr/open-pbs argument
to configure), it didn't work and I got the error message:
--- MCA component pls:tm (m4 configuration macro)
checking for MCA component pls:tm compile mode... dso
checking tm.h usability... yes
checking tm.h presence... yes
checking for tm.h... yes
looking for library in lib
checking for tm_init in -lpbs... no
looking for library in lib64
checking for tm_init in -lpbs... no
checking tm.h usability... yes
checking tm.h presence... yes
checking for tm.h... yes
looking for library in lib
checking for tm_finalize in -ltorque... no
looking for library in lib64
checking for tm_finalize in -ltorque... no
configure: error: TM support requested but not found. Aborting
By looking in the very long configure script I found two typo
errors in variable name:
"ompi_check_tm_hapy" is set at lines 68164 and 76084
"ompi_check_loadleveler_hapy" is set at line 73086
where the correct names are obviously "ompi_check_tm_happy" and
"ompi_check_loadleveler_happy" (e.g. "happy" not "hapy") when
looking to the variables used arround.
I corrected the variables names but unfortunately it didn't fixed
my problem, configure stoped with the same error message (maybe you
should also correct it in your "svn" repository since this may be a
"latent" bug).
I'm now questionning why didn't the configuration script found the
'tm_init' symbol in libpbs.a since the following command:
nm /usr/open-pbs/lib/libpbs.a | grep -e '\<tm_init\>' -e
'\<tm_finalize\>'
prints:
0000000000000cd0 T tm_finalize
0000000000001270 T tm_init
Is it possible that on an EM64T Linux system the configure script
require that lib/libpbs.a or lib64/libpbs.a be a 64 bit library to
be happy (lib64/libpbs.a doesn't exist and lib/libpbs.a is a 32 bit
library on our system since the OpenPBS version we use is a bit old
(2.3.x) and didn't appear to be 64 bit clean) ?
Martin Audet
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
