LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Grismer Matthew J Civ AFRL/VAAC (Matthew.Grismer_at_[hidden])
Date: 2005-08-22 12:27:22


Thanks for the suggestions, yes removing the -fast optimization does fix the
problem of Totalview support not compiling under OS X 10.4.2. I tried it
with -O3, and everything built fine.

 

Matt

 

  _____

From: Grismer Matthew J Civ AFRL/VAAC
Sent: Friday, August 19, 2005 12:53 PM
To: 'lam_at_[hidden]'
Subject: RE: rpi sysv problem on OS X 10.4

 

I'm kind of amazed by this, but the problems with sysv and usysv resolved
themselves after installing the latest SecurityUpdate2005-007 v1.1 from
Apple and rebooting the machine. I'm not sure if it was the security
patches or rebooting the machine, but MPI codes now run fine with the shared
memory rpi's.

 

Regarding the problems with building the Totalview support, here is the
output from the build process when it fails:

 

Making all in totalview

Making all in src

if /bin/sh ../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"\"
-DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\"
-DPACKAGE_BUGREPORT=\"\" -DLAM_WANT_DEBUG=0 -DLAM_CC=\"gcc\"
-Dlam_sizeof_void_p=4 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
-DHAVE_DLFCN_H=1 -I. -I. -I../../../share/include -I../../../share/include
-DLAM_BUILDING=1 -DLAM_BUILDING=1 -D_REENTRANT -DLAM_BUILDING=1 -fast -MT
dll_lam.lo -MD -MP -MF ".deps/dll_lam.Tpo" -c -o dll_lam.lo dll_lam.c; \

then mv -f ".deps/dll_lam.Tpo" ".deps/dll_lam.Plo"; else rm -f
".deps/dll_lam.Tpo"; exit 1; fi

 gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DLAM_WANT_DEBUG=0
-DLAM_CC=\"gcc\" -Dlam_sizeof_void_p=4 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1
-DHAVE_DLFCN_H=1 -I. -I. -I../../../share/include -I../../../share/include
-DLAM_BUILDING=1 -DLAM_BUILDING=1 -D_REENTRANT -DLAM_BUILDING=1 -fast -MT
dll_lam.lo -MD -MP -MF .deps/dll_lam.Tpo -c dll_lam.c -fno-common -DPIC -o
.libs/dll_lam.o

/bin/sh ../libtool --tag=CC --mode=link gcc -fast -o liblam_totalview.la
-rpath /usr/local/lib/lam dll_lam.lo

gcc -dynamiclib ${wl}-flat_namespace ${wl}-undefined ${wl}suppress -o
.libs/liblam_totalview.0.0.0.dylib .libs/dll_lam.o -install_name
/usr/local/lib/lam/liblam_totalview.0.dylib -Wl,-compatibility_version -Wl,1
-Wl,-current_version -Wl,1.0

ld: .libs/dll_lam.o has local relocation entries in non-writable section
(__TEXT,__text)

/usr/bin/libtool: internal link edit command failed

make[3]: *** [liblam_totalview.la] Error 1

make[2]: *** [all-recursive] Error 1

make[1]: *** [all-recursive] Error 1

make: *** [all-recursive] Error 1

 

Matt

 

  _____

From: Grismer Matthew J Civ AFRL/VAAC
Sent: Tuesday, August 16, 2005 3:36 PM
To: 'lam_at_[hidden]'
Subject: rpi sysv problem on OS X 10.4

 

We're building lam-7.2b1r10193 under OS X 10.4.2 on a PowerMac G5, and using
the XL Fortran compiler for Fortran support. We got the XL Fortran compiler
working with mixed C/Fortran code (CC was the default gcc, which is version
4) by adding -lSystemStubs and /usr/lib/libgcc_s.1.0.dylib to the gcc_libs
lines of /etc/opt/ibmcmp/xlf/8.1/xlf.cfg. Lam was configured with the
following:

 

FC=xlf

FFLAGS=-O -qarch=auto -qtune=auto -qcache=auto

CFLAGS=-fast

 

./configure --with-rpi=sysv --with-memory-manager=none --disable-tv-queue

 

The last configure option to disable TotalView support was required to get
the build to complete, so that was the first issue. The second issue is
that neither the sysv or usysv shared-memory rpi's work. When you attempt
to run any code with either of these lam prints the following message:

 

----------------------------------------------------------------------------
-

The selected RPI failed to initialize during MPI_INIT. This is a

fatal error; I must abort.

 

This occurred on host shelob.flight.wpafb.af.mil (n0).

The PID of failed process was 24081 (MPI_COMM_WORLD rank: 0)

 

 

Choosing another rpi, such as lamd or tcp, appears to work fine. Any
suggestions?

 

Matt