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.

Subject: Re: [OMPI devel] [devel-core] OMPI MCA components - track external libs versions
From: Jeff Squyres (jsquyres) (jsquyres_at_[hidden])
Date: 2014-04-14 15:13:03

On Apr 14, 2014, at 2:57 PM, Mike Dubman <miked_at_[hidden]> wrote:

> I think (+know) that many production environments and OMPI users will be happy to have it.

Agreed. Something like:

    char version_str[128];

    snprintf(version_str, sizeof(version_str),
             "%d.%d.%d", libusnic_major, libusnic_minor, libusnic_release);
                                    "Version of the libusnic library",
                                    NULL, 0, 0,


  shell$ ompi_info --param btl usnic --level 9 --parsable | grep version | grep :value:

Make sense?

I suggest level 2 or level 3 for such vars. They shouldn't be in default level 1 ompi_info output, but it is information that may be required to run correctly, so it should be in the "end user" set of info (i.e., be <= 3). See

My point: I don't think you need any new infrastructure for this -- you can do it today.

Jeff Squyres
For corporate legal information go to: