update INSTALL file

[jeffhammond]

The INSTALL file is a bit old.

Here are some issues we should address:

• Jaguar and Blue Gene/P are dead. Let's get the right build examples for contemporary machines like IBM Blue Gene/Q, Cray XC30, etc.
• We do not mention Elemental as an optional capability.
• PC examples related to Mac etc. reference relatively old compilers.
• ...

We should not have examples involving OpenMPI, because it is not reliably thread-safe.

[gifornl]

?Jeff,

Do you have a simple example of openmpi being not thread-safe in the mtm build for 1.8.4?

I have been using this with Intel 15 and gcc 4.8.2 builds. The sys-admins want a simple example that is repeatable...which is not so easy.

Thanks, George

---

From: Jeff Hammond notifications@github.com
Sent: Saturday, October 31, 2015 3:35 PM
To: m-a-d-n-e-s-s/madness
Subject: [madness] update INSTALL file (#162)

The INSTALL file is a bit old.

Here are some issues we should address:

• Jaguar and Blue Gene/P are dead. Let's get the right build examples for contemporary machines like IBM Blue Gene/Q, Cray XC30, etc.
• We do not mention Elemental as an optional capability.
• PC examples related to Mac etc. reference relatively old compilers.
• ...

We should not have examples involving OpenMPI, because it is not reliably thread-safe.

Reply to this email directly or view it on GitHubhttps://github.com//issues/162.

[jeffhammond]

@gifornl I do not have a reproducer handy, because there is no dispute that it is broken (open-mpi/ompi#157). However, there appears to be a complete reproducer on the OpenMPI mailing list.

What's worse than OpenMPI's implementation of MPI_THREAD_MULTIPLE being consistently broken is that it seems to be correct, deadlock or crash, depending on the configuration and usage. I have no patience for such low-quality software.