Thanks for reporting this. We'll put hier back (it looks like it was removed under an incorrect premise).
I've opened ticket https://svn.open-mpi.org/trac/ompi/ticket/3456 to track this issue. On Jan 3, 2013, at 10:26 AM, Ake Sandgren <ake.sandg...@hpc2n.umu.se> wrote: > On Thu, 2013-01-03 at 07:14 -0800, Ralph Castain wrote: >>> Well, it isn't :-) >>> configure says: >>> --- MCA component grpcomm:pmi (m4 configuration macro) >>> checking for MCA component grpcomm:pmi compile mode... dso >>> checking if user requested PMI support... no >>> checking if MCA component grpcomm:pmi can compile... no >> >> Ah - that is the problem. You need to configure >> --with-pmi=<wherever-slurms-pmi.h-is-located> > > Ahh thanks. Was assuming i needed something like that. > >>> Not sure what you mean here. slurm's pmi module is available (and Intel >>> MPI can use it if i point it to it). >> >> Yeah, we need to be pointed to it just like Intel. > > Doh :-( > >>> >>> Anyway, I think that if there is code that tries to use the hier >>> component it shouldn't have been removed. >> >> Agreed - it looks like something picked up an unintended change. Just trying >> to help you work with it as I don't know when a 1.6.4 will occur. > > I pulled the 1.6.1 hier component and reran autogen so i have it working > but it's good to know what's to be expected in later releases. > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
