On Jan 25, 2016, at 6:22 PM, Paul Hargrove <phhargr...@lbl.gov> wrote:
>
> Excellent point about the --with-foo behavior.
> If an admin knows what component name to grep for then they should
> "--with-foo" that component.
> With language bindings the spelling is "--enable-mpi-foo", but the principle
> is the same.
> Adding new places to apply grep is entirely superfluous if use of those
> configure options is applied consistently/correctly.
Agreed. And it's not something that people frequently realize they can do; I
get that.
> Even so, if folks feel (as Nathan or Howard seem to) that a configure summary
> is useful, then I can't see any *harm* in adding it.
> Since once the build is complete ompi_info can tell one essentially
> everything about the build, I don't think Jeff's "slippery slope"/"eye chart"
> concern is a real problem - the summary (if any) would remain very high level
> (such as a list of configured components and language bindings).
Keep in mind:
-----
$ l -d */mca/* | grep '^d' | wc
67 603 4492
$ l -d */mca/*/* | grep '^d' | wc
291 2619 21498
-----
We have ~65 types of components (there's multiple "common"s), and 291
components. I'm not sure how to show a summary of them.
If people want to print a summary at the end of configure, that's fine. But
one of the mails said that we want to show schedulers and networks (today). I
think that covers the following frameworks:
ras, plm, pml, mtl, btl, oob
Can someone propose/mock up an output could look like using the real framework
and component names?
> If at the end of this line of discussion no new summary output is to be
> generated, then I stand my original proposal of having "make install" print a
> suggestion that admins run ompi_info to double-check what they have
> built/installed.
> That helps the admin who doesn't know the name of the component for passing
> --with-foo, but might recognize it when they see it (e.g.
> "ofi"-vs-"libfabric", "verbs"-vs-"ibv", or "pbs"-vs-"tm").
I have no problem with that.
(...I actually meant to send this last night and forgot... But it's ok,
because we talked about this topic on the Tuesday telecom, and decided to keep
thinking about it -- whatever solution we come up with will likely need to be a
bit creative. Probably a good topic for the Dallas face-to-face meeting:
https://github.com/open-mpi/ompi/wiki/Meeting-2016-02)
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
