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

[Novosielski, Ryan]

My original message with the log files attached got held for size. Here is another send with the files compressed. As I said below:

>> 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.<config.log-2.1rc2><config.log-2.0.1>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log-2.1rc2.gz
Type: application/x-gzip
Size: 29059 bytes
Desc: config.log-2.1rc2.gz
URL: <http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/attachments/20150331/99fec584/attachment-0002.gz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log-2.0.1.gz
Type: application/x-gzip
Size: 29596 bytes
Desc: config.log-2.0.1.gz
URL: <http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/attachments/20150331/99fec584/attachment-0003.gz>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/attachments/20150331/99fec584/attachment-0001.txt>