Changes between Version 21 and Version 22 of babelbgp

Timestamp:

02/24/09 22:40:08 (14 years ago)

Author:

norris

Comment:

--

babelbgp

@@ -37 +37 @@
 Some 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]. 
 
+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 ----
+    fi
+  
+    if test "X$enable_python" != "Xno"; then
++     if test "X$cross_compiling" != "Xyes"; then 
+        LLNL_PYTHON_LIBRARY
+        LLNL_PYTHON_NUMERIC
+        LLNL_PYTHON_SHARED_LIBRARY
+        LLNL_PYTHON_AIX
++     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
+         enable_python=no;
+         AC_MSG_WARN([Configuration for Python failed.  Support for Python disabled!])
+}}}
+
 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:
 {{{