Changes between Version 36 and Version 37 of babelbgp

Timestamp:

10/16/09 15:01:15 (13 years ago)

Author:

tramer

Comment:

--

babelbgp

@@ -3 +3 @@
 ==== Current build instructions (Notes by Stephen Tramer [mailto:[email protected]]) ====
 
-It is strongly recommended that you make a directory on /scratch to perform your build in.  Boyana mentions in her notes below that configure/make takes a long time; this is because of the slow disk access to $HOME on login nodes for surveyor.  Configure and builds proceed much faster on /scratch.
+It is strongly recommended that you make a directory on /scratch to perform your build in.  Boyana mentions in her notes below that configure/make takes a long time; this is because of the slow disk access to $HOME on login nodes for surveyor.  Configure and builds proceed much faster on /scratch.  '''However, note that you cannot run the regression tests from /scratch.'''  This is because /scratch is specific to each login node, and is not mounted for any BG/P nodes.
 
 These notes very closely follow Boyana's, but some of her fixes have now been patched into the code.  For the full details of what has been modified in order to support BG/P, please see below.
@@ -9 +9 @@
 These instructions will enable support for all languages except java (irrelevant on BG/P, since it doesn't have java).  Throughout $BABEL_SRC will refer to your local babel source copy and $BABEL_INSTALL to the directory where babel will be installed.  Please be aware that this build process has been tested only in the development branch, for the proposed babel 1.5.0.
 
-1. Build a local version of libxml2 (if you want).  There is a version available at /home/tramer/libxml-bgp, compiled for use with applications being compiled for BG/P.  However, it is recommended that you roll your own to become familiar with some issues with cross-compiling using the GNU autotools.  However, if you do this, you will need to run the $BABEL_SRC/contrb/libtool_fix.sh script to patch up the generated libtool files, and be aware that you will need to use the '-qnostaticlink' LDFLAG setting.
+1. Build a local version of libxml2 (if you want) and also libtool (if you like).  There are versions available at /home/tramer/libxml2-bgp and /home/tramer/libtool-dev-bgp respectively, compiled for use with applications being compiled for BG/P.  However, it is recommended that you roll your own to become familiar with some issues with cross-compiling using the GNU autotools.  See Boyana's instructions below for libxml2; for libtool you will need to run 'make' first and ''then'' the libtool_fix.sh script.
 
 2. Configure the project:
 
 {{{
-$BABEL_SRC/configure CPP="gcc -E" CC=mpixlc CXX=mpixlcxx FC=mpixlf2003 F77=mpixlf77 --with-bindc --prefix=$BABEL_INSTALL \
-  --host=powerpc-bgp-linux-gnu --target=powerpc64-ibm-bgp --without-sidlx --with-gcc=no \
-  --enable-python=/bgsys/drivers/ppcfloor/gnu-linux/bin/python target_alias=powerpc64-ibm-bgp \
-  --with-libxml2=$LIBXML2_LOCATION --without-libparsifal LDFLAGS="-G -qnostaticlink" host_alias=powerpc-bgp-linux-gnu
-}}}
+$BABEL_SRC/configure CC=bgxlc CXX=bgxlC FC=bgxlf90 F77=bgxlf --prefix=$BABEL_INSTALL_DIR --host=powerpc-bgp-linux-gnu \
+  --without-sidlx --with-gcc=no --enable-python=/bgsys/drivers/ppcfloor/gnu-linux/bin/python \
+  --with-libxml2=$LIBXML2_DIR LDFLAGS=-qnostaticlink --enable-shared --disable-static \
+  host_alias=powerpc-bgp-linux-gnu --target=powerpc64-ibm-bgp --with-ltdl-lib=$LIBTOOL_DIR/lib \
+  --with-ltdl-include=$LIBTOOL_DIR/include --without-libparsifal --disable-fortran90
+}}}
+
+You may also use the mpixl* compilers if you wish.  However since babel does not use MPI, this is not necessary.  Currently --disable-fortran90 is only needed because struct support is currently broken in babel; it should be safe to add it back in.  Also note that you can build the convenience ltdl contained within babel itself - use the external libtool only if this doesn't work.
 
 If the configure fails, run aclocal, autoconf, and automake in both $BABEL_SRC and $BABEL_SRC/runtime.  Note that you will need autoconf 2.64 and automake 1.10.x; these are not available on the login machines and you will have to build them yourself (but do not need to port them to BG/P; they will only be used for building).
 
-If your configure fails, please look at Boyana's instructions below and examine your output to determine where the mistake could be.
+If your configure fails, please look at Boyana's instructions below and examine your output to determine where the mistake could be.  However, note that you should '''not''' include '-G' in the LDFLAGS.  This flag is for building libraries only; providing it to an executable build will cause severe problems.
 
 3. Run $BABEL_SRC/contrib/libtool_fix.sh in the $BABEL_SRC directory.  This will patch your libtool files so that they are compatible with the BG/P compilers.  '''Do not skip this step.  If step 4 fails, make sure you have done this.'''
@@ -28 +31 @@
 4. 'make clean all install'
 
-If your make fails, please look at Boyana's instructions below and examine your output to determine where the mistake could be.  A last resort is to build the latest development version of libtool, which has some preliminary BG/P support rolled into it.  You can get instructions on how to obtain it from [http://www.gnu.org/software/libtool/ the GNU libtool project page].  You WILL need to build libtool for BG/P so that it is possible to link against the ltdl libraries.  If you're frightened of rolling your own, you can use the libtool available in /home/tramer/libtool-dev-bgp.  Note that you will still need the latest (stable) aclocal, autoconf, and automake to get the dev libtool to work.
+If your make fails, please look at Boyana's instructions below and examine your output to determine where the mistake could be.
+
+==== Running regression tests ====
+
+Again, '''you cannot run regression tests from /scratch.'''  Trying to do so will cause headaches and a complete lack of output from mpirun.  Build your babel source in your home directory (or another directory mounted by the BG/P) in order to run regression tests.
+
+Note that currently there is no automation for running babel tests on the BG/P; you will have to run them by hand.  Therefore it is recommended that you only run a handful; the struct and array tests are most useful since they involve data alignment and can be used to detect any issues of that sort.  You can run a regression test by:
+
+1. Edit the libtool convenience script for 'runAll' in the test of your choice:
+
+{{{
+[email protected]:~/babel/trunk/regression/arrays/runC> diff runAll runAll.cobalt 
+135c135,138
+<       exec "$progdir/$program" ${1+"[email protected]"}
+---
+>       cobalt-mpirun -mode vn -np 1 -verbose 2 -cwd `pwd` -env "LD_LIBRARY_PATH=${LD_LIBRARY_PATH} SIDL_DLL_PATH=${SIDL_DLL_PATH}" \
+>         "$progdir/$program" ${1+"[email protected]"}
+
+}}}
+
+2. 'qsub --mode script -A cca-tools -t 15 -n 1 runAll.sh'
+
+3. Once the job completes on the BG/P nodes, you will have to manually examine the test output for failures.  Please note that tests will (erroneously) marked as BROKEN due to the return value of cobalt-mpirun from the libtool convenience script.  Actual broken tests can only be checked by examining the output and error logs.
 
 ==== Old build instructions (Notes by Boyana Norris [mailto:[email protected]]) ====