Version 30 (modified by tramer, 13 years ago) (diff)


Installing Babel on BG/P (Surveyor at Argonne)

Current build instructions (Notes by Stephen Tramer [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.

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.

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/ script to patch up the generated libtool files, and be aware that you will need to use the '-qnostaticlink' LDFLAG setting.
  1. 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

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).

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 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 configure fails, please look at Boyana's instructions below and examine your output to determine where the mistake could be.

  1. Run $BABEL_SRC/contrib/ 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.
  1. '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.

Old build instructions (Notes by Boyana Norris [email protected]…)

I do not recommend that anyone tries this unless they want to spend a lot of time waiting for configure scripts to complete (e.g., on my laptop, babel configure takes 2.5 minutes, while on the BG/P it takes at least 20 minutes, depending on various options, and then you have to actually build).

  1. First of all, I started out with the goal of getting as many languages supported as possible, including python. This necessitated the following steps:
    1. Python distutils are rather crippled when it comes to cross-compiling. I built my own python (version 2.6.1) and extended the distutils implementation with a BG/P-specific compiler module. More details on that are available here.
    2. I had to install NumPy , which turned out to be nontrivial (see description). My second requirement was support for shared libraries since fully static builds are (1) less flexible; and (2) not quite fully automated for CCA components. There is also the additional danger of running out of memory because of bloated static executables. GNU Libtool does not work out of the box for building shared libraries on the BG/P -- more on that later.
  1. As expected, GNU Autotools-based packages cannot be simply built on BG/P. First, configure does not provide good cross-compilation support, at least not good enough for BG/P. I added these settings to the llnl_cross_compiling.m4 file (right after the case "$target" in line):
        llnl_cv_F77_string_passing="far int32_t"
        llnl_cv_F90_string_passing="far int32_t"

Some additional hard-coded configure settings are discussed in this IBM Document. (Note: A host triplet used for identifying compute nodes (used by IBM)seems to be powerpc-bgp-linux (not the one above).)

Next I changed the runtime/m4/llnl_confirm_babel_python.m4 file as follows:

*** llnl_confirm_babel_python_support.m4	2008-10-21 12:05:31.000000000 -0500
--- /home/norris/babel-1.4.0/runtime/m4/llnl_confirm_babel_python_support.m4	2009-02-24 22:38:39.246831463 -0600
*** 38,47 ****
--- 38,49 ----
    if test "X$enable_python" != "Xno"; then
+     if test "X$cross_compiling" != "Xyes"; then 
+     fi
      if test \( "X$llnl_cv_python_numerical" != "Xyes" -a  "X$llnl_cv_python_numpy" != "Xyes" \) -o "X$enable_shared" = "Xno" -o "X$XML2_CONFIG" = "Xno"; then
         AC_MSG_WARN([Configuration for Python failed.  Support for Python disabled!])

(NOTE from Tramer: This change was not necessary for the new BG/P cross-compilation, and in fact broke the build.)

Finally, I modified runtime/config/config.sub as follows:

*** config.sub	2008-10-21 11:42:24.000000000 -0500
--- /home/norris/babel-1.4.0.bk/runtime/config/config.sub	2009-02-23 13:23:35.376490273 -0600
*** 1391,1396 ****
--- 1391,1399 ----
+ 	-bgp)
+ 		os=-bgp
+ 		;;

While building prerequisites (see next item), I found that libtool did not support building and linking shared libraries using IBM's compilers. The perfect fix for this problem is to add BG/P support to libtool. The faster workaround was to first set an environment variable:

export LDFLAGS='-G -qnostaticlink'

then run configure. Next we introduce an extra step before running make by using this little script on all generated libtool scripts in the build directory of the package being built



if test "x$1" = "x" ; then prog=libtool
else prog=$1; fi

find $wd -name $prog -exec \
    sed -i1 -e 's|^export_dynamic_flag_spec=.*$|export_dynamic_flag_spec=""|g' \
        -e 's|^whole_archive_flag_spec=.$|whole_archive_flag_spec=""|g' \
	-e 's|^pic_flag=.*$|pic_flag=" -DPIC -qpic"|g' \
	-e 's|^archive_cmds=.*$|archive_cmds="\\$CC -G \\$libobjs \\$deplibs \\$compiler_flags -qmkshrobj -e \\$soname  -o \\$lib"|g' \
	-e 's|^hardcode_libdir_flag_spec=.*$|hardcode_libdir_flag_spec="-R\\$libdir -L\\$libdir"|g' {} \; -print

  1. To successfully configure Babel, the following prerequisites were necessary: libxml2 and zlib. The former was required for Python support (so the fact that Babel includes libparsifal does not remove the dependence on libxml2 if you want Python). The latter was required by libxml2.
    1. zlib-1.2.3 was configured with:
      ./configure --prefix=/home/norris/cca
      and then I had to manually change the values of the CC and LDSHARED variables since zlib does not have a real configure. The values were CC=mpixlc and LDSHARED=mpixlc (I think you only really need CC).

    2. libxml2-2.7.3 was configured and built with
      ./configure --prefix=/home/norris/cca CC=mpixlc CXX=mpixlcxx F90=mpixlf2003 F77=mpixlf77 \
        CPP='gcc -E' --with-python=/bgsys/drivers/ppcfloor/gnu-linux/bin/python --with-zlib=/home/norris/cca \
        --enable-shared --disable-static
      make install