More specifically building the new “flang” compiler and compiling openmpi
with the combination of clang/flang rather than clang/gfortran.
Configure is passing (including support for 16 byte REAL and COMPLEX
types. However there is one file that uses REAL128 and CONPLE(REAL128) and
I’m getting typ
As request I've attached the config.log. I also included the output from
configure itself.
-Alan
On Fri, Sep 14, 2018, 10:20 AM Alan Wild wrote:
> I apologize if this has been discussed before but I've been unable to find
> discussion on the topic.
>
> I recently went
I apologize if this has been discussed before but I've been unable to find
discussion on the topic.
I recently went to build 3.1.2 on our cluster only to have the build
completely fail during configure due to issues with libnl versions.
Specifically I was had requested support for mellanox's lib
Sorry I didn't get back to your right away. 1) I'm on the digest, 2) not
real familiar with git and 3) just learned the hard way how to update the
build to work with the latest versions of automake, autoconf, and libtool.
:)
Anyway, I believe the patch is an improvement. Looking at it, I can tel
I know this isn't "recommend", but a vendor recently gave me an executable
compiled openmpi-1.8.3 and I happened to have recently completed a build of
1.8.4 (but didn't have 1.8.3 sitting around and the vendor refuses to
provide his build).
Since these releases are so close they should be ABI comp
I'm surprised that there are users still reporting issues getting this to
work, but as I'm still seeing notes in the digest I wanted to share (what I
believe the issue is) and how I've fixed it.
If you don't take special measures, OpenMPI will be dynamically linked and
have runtime dependencies on
I recently installed 1.6.2 on our cluster only to be introduced to the new
warning messages concerning registerable memory and physical memory.
OpenMPI is indicating:
Registerable memory: 32768 MiB
Total memory:48434 MiB
Which is clearly less than the "3/4 total memory" that pr
