Re: [OMPI users] Absoft compilation problem
I unfortunately do not have access to an Absoft compiler to test this with; it looks like GNU Libtool is getting the wrong arguments to pass to the f95 compiler to build a shared library. A quick workaround for this issue would be to disable the MPI F90 bindings with the --disable-mpi-f90 switch to configure. Could you try the Open MPI nightly trunk tarball and see if it works there? We use a different version of Libtool to make those tarballs. On Jun 30, 2007, at 2:09 AM, Yip, Elizabeth L wrote: The attachment shows my problems when I tried to compile openmpi 1.2.3 with absoft 95 (Absoft 64-bit Fortran 95 9.0 with Service Pack 1). I have similar problems with version 1.2.1, but no problem with version 1.2.1. Elizabeth Yip -- Jeff Squyres Cisco Systems
Re: [OMPI users] openmpi on g4 mac with g95 (www.g95.org) in mpif90
Please see the "Getting Help" page on the OMPI web site (look in the links in the navigation on the left-hand side) -- we need some more information from you in order to correctly diagnose the problem. Thanks. On Jun 30, 2007, at 5:50 AM, Ed D'Azevedo wrote: I am trying to build openmpi on a G4 mac osx 10.4 with Fortran g95 (www.g95.org) support. I would like to use mpif90 or mpif77 to compile Fortran MPI code.I get an error in the configuration script. I use "sh setup.sh". The file "setup.sh" is attached. Is there a way to make a reasonable guess say Fortran logical is the same size as Fortran integer and continue with the build process? Thanks. checking if PowerPC registers have r prefix... yes checking for 64-bit PowerPC assembly support... no checking if gcc supports GCC inline assembly... yes checking if gcc supports DEC inline assembly... no checking if gcc supports XLC inline assembly... no checking if g++ supports GCC inline assembly... yes checking if g++ supports DEC inline assembly... no checking if g++ supports XLC inline assembly... no checking for assembly format... default-.text-.globl-:-_-L--0-1-1-0-0 checking for asssembly architecture... POWERPC32 checking for perl... perl checking for pre-built assembly file... yes (atomic-powerpc32- osx.s) checking for atomic assembly filename... atomic-powerpc32- osx.s *** Fortran 77 compiler checking whether we are using the GNU Fortran 77 compiler... yes checking whether /Users/e6d/bin/g95 accepts -g... yes checking if Fortran 77 compiler works... yes checking /Users/e6d/bin/g95 external symbol convention... double underscore checking if C and Fortran 77 are link compatible... yes checking if Fortran 77 compiler supports LOGICAL... yes checking size of Fortran 77 LOGICAL... configure: error: Could not determine size of LOGICAL F77=/Users/e6d/bin/g95 FFLAGS="-ffixed-form -i4 -fzero -g -ftrace=full" FC=/Users/e6d/bin/g95 FCFLAGS="-i4 -fzero -g -ftrace=full" export F77 export FFLAGS export FC export FCFLAGS ./configure --enable-mpi-f90 \ --with-mpi-f90-size=trivial \ --with-mpi-param-check=always \ F77=/Users/e6d/bin/g95 \ FC=/Users/e6d/bin/g95 \ FFLAGS=" -ffixed-form -i4 -fzero -g -ftrace=full " \ FCFLAGS=" -ffixed-form -i4 -fzero -g -ftrace=full " ___ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres Cisco Systems
Re: [OMPI users] initial setup
I'm not a bash user -- but don't you need to export PATH, LD_LIBRARY_PATH, and MANPATH? It could be that something else later is exporting PATH (and therefore your changes "take effect"), but nothing exports LD_LIBRARY_PATH (and therefore your changes get lost). On Jun 28, 2007, at 12:34 AM, Adams, Samuel D Contr AFRL/HEDR wrote: I have something wrong with having my LD_LIBRARY_PATH variable path set when I am doing a non-interactive login to remote nodes. These nodes are running RHEL5. It looks like something like this: [sam@prodnode1 fdtd_0.3]$ time mpiexec --host prodnode3 -np 16 fdtd -t ./test_files/tissue.txt -r ./test_files/sphere_x0120y0120z0120.raw -v Beowulf Computer Cluster (BCC) AFRL/HED ... Setting up [gcc production] cluster environment fdtd: error while loading shared libraries: libmpi.so.0: cannot open shared object file: No such file or directory ... For some reason the LD_LIBRARY_PATH is not being set, but the PATH is: -- [sam@prodnode1 ~]$ ssh prodnode3 export Beowulf Computer Cluster (BCC) AFRL/HED ... Setting up [gcc production] cluster environment declare -x G_BROKEN_FILENAMES="1" declare -x HOME="/home/sam" declare -x LANG="en_US.UTF-8" declare -x LESSOPEN="|/usr/bin/lesspipe.sh %s" declare -x LOGNAME="sam" declare -x LS_COLORS="" declare -x MAIL="/var/mail/sam" declare -x OLDPWD declare -x PATH="/usr/local/profiles/gcc-openmpi/bin/:/usr/kerberos/bin:/usr/ local/ bin:/bin:/usr/bin:/opt/jdk1.5.0_07/bin" declare -x PWD="/home/sam" declare -x SHELL="/bin/bash" declare -x SHLVL="1" declare -x SSH_CLIENT="140.140.207.111 51258 22" declare -x SSH_CONNECTION="140.140.207.111 51258 140.140.207.113 22" declare -x USER="sam" [sam@prodnode1 ~]$ I have the following in both my .bashrc and .profile in $HOME: if [ `hostname | grep "prod"` ]; then echo "Setting up [gcc production] cluster environment" PATH=/usr/local/profiles/gcc-openmpi/bin/:$PATH LD_LIBRARY_PATH=/usr/local/profiles/gcc-openmpi/lib/:$LD_LIBRARY_PATH MANPATH=/usr/local/profiles/gcc-openmpi/man:$MANPATH fi Things will work if I use: $ mpirun --prefix /usr/local/profiles/gcc-openmpi ... Sam Adams General Dynamics Information Technology Phone: 210.536.5945 ___ users mailing list us...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres Cisco Systems
