On Jan 23, 2013, at 3:35 PM CST, Jed Brown wrote:

On Wed, Jan 23, 2013 at 2:44 PM, Dave Goodell <[email protected]> wrote:

...

A run-time test that doesn't require looking at which symbols are compiled into the app? I can't think of one off the top of my head, although I suppose we could add one in the future via either MPI_T or the new MPI_Get_library_version routine.

A configure-time test is fine. I can look for symbols in libmpich.a, for example. Is something exported that would be proof-positive of ch3:sock? We would like to avoid _running_ MPI code at configure time because many machines prevent anything that links MPI from running on an interactive node.

I think checking of the "MPIDI_CH3I_sock_errno_to_mpi_errno" symbol should be unique enough to detect ch3:sock. -Dave