I don’t think there’s a good answer for this. The file maint/version.m4 is where we keep the ABI string: m4_define([libmpi_so_version_m4],[0:0:0]) Obviously, that’s pretty terrible to try to parse for a user. Also, in unreleased versions, those numbers will remain 0. It’s just in tarballs that the number will be updated. Otherwise, you can get the name at the end of your shared library string that libtool appends. If this is important, we’ll have to figure out something for future versions. Thanks, Wesley

On Feb 19, 2015, at 2:52 PM, Jeff Hammond <[email protected]> wrote:

How do I query the MPICH ABI information at compile and run time? I grepped the source and it isn't obvious.

Are there preprocess symbols in mpi.h? I didn't see them.

Is the ABI version encoded in the output of MPI_Get_library_version? I have not tested this myself, for which I am deeply sorry. If I am adverse to string parsing, is there a way to get this information more directly from the tools interface, or perhaps as a non-standard attribute on MPI_COMM_WORLD?

Is there a way to encode the ABI version in the binary itself via something like MPICH_ABI_SYMBOL_1_1?

I do not want to rely upon any mechanism that is associated with shared libraries, because I want a solution that works with CrayMPI when linking static binaries.

Thanks,

Jeff

-- Jeff Hammond [email protected] http://jeffhammond.github.io/ _______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss