Changes between Version 15 and Version 16 of babelbgp


Ignore:
Timestamp:
02/24/09 21:47:44 (14 years ago)
Author:
norris
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • babelbgp

    v15 v16  
    33I 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).  
    44 
    5 1.  First of all, I started out with the goal of getting as many languages supported as possible, including python. This meant that I had to install !NumPy first, which turned out to be nontrivial (see [wiki:ccanumpy description]). 
     51.  First of all, I started out with the goal of getting as many languages supported as possible, including python. This meant that I had to install !NumPy first, which turned out to be nontrivial (see [wiki:ccanumpy description]). The 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. 
    66 
    7 2. I discovered that the following prerequisites were necessary: libxml2, then 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. [[BR]] 
     72. 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: 
     8{{{ 
     9  powerpc64-ibm-bgp*) 
     10    cross_compiling=yes 
     11    llnl_cross_compiling_okay=yes 
     12    enable_pure_static_runtime=no 
     13    enable_shared=yes 
     14    enable_static=no 
     15    enable_java=no 
     16    enable_python=/bgsys/drivers/ppcfloor/gnu-linux/bin/python 
     17    llnl_cv_python_prefix=/bgsys/drivers/ppcfloor/gnu-linux 
     18    llnl_cv_python_numpy=yes 
     19    llnl_cv_python_library=$llnl_cv_python_prefix/lib 
     20    llnl_cv_python_version=2.5 
     21    llnl_cv_python_include=$llnl_cv_python_prefix/include/python$llnl_cv_python_version 
     22    llnl_python_shared_library=$llnl_cv_python_library/libpython2.5.so 
     23    llnl_python_shared_library_found=yes 
     24    sidl_cv_f77_false=0 
     25    sidl_cv_f77_true=1 
     26    sidl_cv_f90_false=0 
     27    sidl_cv_f90_true=1 
     28    llnl_cv_F77_string_passing="far int32_t" 
     29    llnl_cv_F90_string_passing="far int32_t" 
     30    ac_cv_func_malloc_0_nonnull=yes 
     31    ac_cv_func_realloc_0_nonnull=yes 
     32    ac_cv_func_memcmp_working=yes 
     33    with_sidlx=no 
     34    ;; 
     35}}} 
     36Some additional hard-coded configure settings are discussed in this [http://www-03.ibm.com/support/techdocs/atsmastr.nsf/5cb5ed706d254a8186256c71006d2e0a/e4342b26ffc557cc862573a80019767d/$FILE/OSS_on_BGP.pdf IBM Document].  
     37 
     383. I discovered that the following prerequisites were necessary: libxml2, then 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. [[BR]] 
    839  a. zlib-1.2.3 was configured with: 
    940  {{{