[mvapich-discuss] Docs re: MVAPICH2 2.0.x and PBS/Torque

[Jonathan Perkins]

In my earlier reply I didn't intend for you to replace the source code of
the src/pm/hydra directory.  If you where to do that it is possible that
things may work but that adds some more unknowns for me.

I think it'll just be simpler to build and install MV2 as normal, then
build and install the hydra package as an additional step.  I meant to send
out the link earlier.  The standalone hydra package can be found at
http://www.mpich.org/static/downloads/3.1.4/hydra-3.1.4.tar.gz.


On Tue, Mar 31, 2015 at 3:12 PM Novosielski, Ryan <novosirj at ca.rutgers.edu>
wrote:

> I will give it a shot. Do you mean just replace the src/pm/hydra directory
> in the 2.0.1 tree with the newer copy from 2.1rc2? How would you recommend
> going about the procedure? Do a regular configure/make/make install, then
> cd to a replaced copy of src/pm/hydra and do a new configure/make/make
> install there, or do I do a new configure at the top level and a new
> make/make install at src/pm/hydra?
>
> Unless I’m misunderstanding, might it not be necessary to build without
> --with-pbs and then build newer hydra --with-pbs it, since I’m replacing
> the problem code with newer code?
>
> Thank you for your quick replies!
>
> > On Mar 31, 2015, at 2:41 PM, Jonathan Perkins <
> perkinjo at cse.ohio-state.edu> wrote:
> >
> > Hi Ryan.  I wasn't sure if it would pass or not but I believe that there
> may have been some changes in hydra between the releases.  May I suggest
> that you try using hydra-3.1.4 with MVAPICH2-2.0.1.  You should be able to
> build MVAPICH2-2.0.1 without the --with-pbs option and then build the hydra
> package with the --with-pbs option.  Specify the same prefix and the newer
> hydra will replace the older hydra.
> >
> > Hopefully this will work for you.  I haven't tried it myself but I don't
> see any issues that should prevent this from working.
> >
> > On Tue, Mar 31, 2015 at 2:26 PM Novosielski, Ryan <
> novosirj at ca.rutgers.edu> wrote:
> > Huh, so, 2.1rc2 does not fail. Can we figure out what’s wrong with 2.0
> and 2.0.1 that does cause them to fail so that I can patch them or use a
> workaround to recompile these to be Torque-aware? These versions are still
> in use and it would take awhile to rebuild the software that I’d have to
> rebuild in order to stop using those versions entirely.
> >
> > I’ve attached the config.log, in case you were expecting this would not
> fail and that’s what you meant. Just because I suspect it might help, I’m
> also attaching the config.log from a failed attempt at compiling 2.0.1 with
> the exact same flags. Ignore the —prefix in the 2.1rc2 log that might lead
> one to believe it’s 2.0.1.
>
> ____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
> || \\UTGERS      |---------------------*O*---------------------
> ||_// Biomedical | Ryan Novosielski - Senior Technologist
> || \\ and Health | novosirj at rutgers.edu - 973/972.0922 (2x0922)
> ||  \\  Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark
>      `'
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/attachments/20150331/0275a04f/attachment.html>