Re: [OMPI devel] Notes on building and running Open MPI on Red Storm
Thanks for the heads up. I've noticed this warning on the Cray systems here at ORNL, and haven't had a chance to put the fix in yet. This function is exposed in non-CR builds as a user interface item. If the user requests a checkpoint of an MPI job that was not compiled with C/R (or doesn't have it enabled if FT was compiled in) then it will respond with a nice error message instead of not responding at all. I go back and forth on cutting this out completely as the tools to checkpoint shouldn't be built if a user doesn't compile in FT support. I'll work on a fix for it in the next couple of days. Cheers, Josh On Jul 12, 2007, at 10:40 AM, Brian Barrett wrote: On Jul 11, 2007, at 4:47 PM, Glendenning, Lisa wrote: * When linking with libopen-pal, the following warning is normal: 'In function `checkpoint_response': warning: mkfifo is not implemented and will always fail' Josh - I thought the checkpoint code wasn't built unless requested. Anyway, if you AC_CHECK_FUNCS for mkfifo, it'll fail on the Cray. Can you update opal/runtime/opal_cr.c to not have code that calls mkfifo() compiled on platforms that don't have mkfifo? Thanks, Brian ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel Josh Hursey jjhur...@open-mpi.org http://www.open-mpi.org/
Re: [OMPI devel] Notes on building and running Open MPI on Red Storm
Do you have a Subversion account? If so, feel free to update the wiki ;). If not, we should probably get you an account. Then feel free to update the wiki ;). But thanks for the notes! Brian On Jul 11, 2007, at 4:47 PM, Glendenning, Lisa wrote: Some supplementary information to the wiki at https://svn.open-mpi.org/trac/ompi/wiki/CrayXT3. I. Accessing the Open MPI source: * Subversion is installed on redstorm in /projects/unsupported/bin * Reddish has subversion in the default path (you don't have to load a module) * The proxy information in the wiki is accurate, and works on both redstorm and reddish II. Building Open MPI on reddish: * 'module load PrgEnv-pgi-xc' to cross compile for redstorm * Reddish and redstorm do not have recent enough version of autotools, so you must build your own (currently available in /project/openmpi/rbbrigh/tools) * Suggested configuration: 'configure CC=qk-gcc CXX=qk-pgCC F77=qk-pgf77 FC=qk-pgf90 --disable-mpi-profile --with- platform=redstorm --host=x86_64-cray-linux-gnu --build=x86_64-unknown-linux-gnu --disable-mpi-f90 --disable-mem-debug --disable-mem-profile --disable-debug build_alias=x86_64-unknown-linux-gnu host_alias=x86_64-cray-linux-gnu' III. Building with Open MPI: * No executables will be installed in $PREFIX/bin, so must compile without mpicc, e.g. 'qk-gcc -I$PREFIX/include *.c -L$PREFIX/lib -lmpi -lopen-rte -lopen-pal' * When linking with libopen-pal, the following warning is normal: 'In function `checkpoint_response': warning: mkfifo is not implemented and will always fail' IV. Running on Redstorm: * scp your executable from reddish to redstorm * Use 'qsub' to submit job and 'yod' to launch job (if you do an interactive session, you can bypass PBS) * qsub expects project/task information - you can either provide this with -A option or set it in $XT_ACCOUNT environmental variable * Sample job script for qsub with 8 nodes/processes and 10 minute runtime: #!/bin/sh #PBS -lsize=8 #PBS -lwalltime=10:00 cd $PBS_O_WORKDIR yod a.out * Use 'xtshowmesh' and 'qstat' to query job status and cluster configuration ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel
