Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

From: Brian Barrett (bbarrett_at_[hidden])
Date: 2007-06-20 11:35:59

Following up on the telecon conversation about automatically forcing
components to build statically (ie, part of libmpi and friends
instead of a stand-alone dso), here's an example of how to do so:

AC_DEFUN([MCA_backtrace_darwin_COMPILE_MODE], [
     AC_MSG_CHECKING([for MCA component $2:$3 compile mode])


     AS_IF([test "$DSO_$2" = "1" -o "$DSO_$2_$3" = "1"],
       [AC_MSG_WARN([Forcing static build of component])])

This snippet of M4 would go in the configure.m4 for the given
component (a configure.m4 is *required* for this). Just change the
backtrace_darwin to the framework_component pair for the given
component, reautogen, and life is good. The various OPAL components
currently in the trunk that use this trick do not have the if check
at the bottom to warn the user that the component changed what the
user said to do, but it probably makes sense to do so in the general
case and I'll be updating the OPAL components in the near future.