KNC is effectively dead. Remove corresponding SCIF
support in Open MPI.
cherry pick of PR #5737
+
news update
Signed-off-by: Howard Pritchard <howardp@lanl.gov>
(cherry picked from commit b9ac3d8931)
some clean up of old cruft for configure options that
we should have cleaned up a while ago.
[skip ci]
Signed-off-by: Howard Pritchard <howardp@lanl.gov>
This option isn't needed on modern distros; add a note to README about
it.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
(cherry picked from commit 9a8b0d0e18)
As documented in #4563 and #3697, there is an issue on ARM and
POWER platforms when the atomic fifo assembly isn't inlined,
which manifests as a hang. Document the issue and the
work-around until a proper fix is committed.
Signed-off-by: Brian Barrett <bbarrett@amazon.com>
Give packagers a configure CLI option to set the value of the MCA
variable mca_base_component_show_load_errors.
The --disable form of this option is intended for Open MPI packagers
who tend to enable support for many different types of networks and
systems in their packages. For example, consider a packager who
includes support for both the FOO and BAR networks in their Open MPI
package, both of which require support libraries (libFOO.so and
libBAR.so). If an end user only has BAR hardware, they likely only
have libBAR.so available on their systems -- not libFOO.so. Disabling
load errors by default will prevent the user from seeing potentially
confusing warnings about the FOO components failing to load because
libFOO.so is not available on their systems.
Conversely, system administrators tend to build an Open MPI that is
targeted at their specific environment, and contains few (if any)
components that are not needed. In such cases, they might want their
users to be warned that the FOO network components failed to load
(e.g., if libFOO.so was mistakenly unavailable), because Open MPI may
otherwise silently failover to a slower network path for MPI traffic.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
The clang 4.0 compiler that ships with FreeBSD 11.1 doesn't
work well with OpenMPI. Workaround is to use a GNU compiler.
Related to #3992.
[skip ci]
Signed-off-by: Howard Pritchard <howardp@lanl.gov>
Move Pathscale bullets closer to each other.
Also add a (sad) note that as of July 2017, the Pathscale compiler
suite no longer has any commercial support, and it does not look like
there will be any further releases.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
Per discussions at the OMPI devel f2f 7/17
we decided for ARM to drop support for ARMv4/v5.
[skip ci]
Signed-off-by: Howard Pritchard <howardp@lanl.gov>
* Related to Issue #2606 and Issue #3075
* The core problem in those two issues is related to a regression in
ld upstream. Add a note in the README about this issue.
Signed-off-by: Joshua Hursey <jhursey@us.ibm.com>
Lots of people still use GFortran, and lots of people still use
somewhat old versions of it (e.g., if it's bundled in their
older-but-still-installed Linux distros). So let's specifically
mention it. This may be a bit overkill, but more specific docs are
usually a Good Thing (i.e., they can prevent questions from being sent
to the mailing list).
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
- MPI bindings build/link correctly, so remove note about that.
- OpenSHMEM bindings do not build/link correctly by default.
- Note the workaround and the issue on GitHub for users.
Signed-off-by: Joshua Hursey <jhursey@us.ibm.com>
The --enable-new-dtags option for the compiler wrappers is
often great, but for some particular install/usage scenarios
causes issues.
This commit provides a new configury option to use of rpath
in the compiler wrappers, but disables the
use of --enable-new-dtags in the link line.
The new configury option is
--enable-wrappers-runpath
To disable use of --enable-new-dtags in the wrappers, add
--disable-wrappers-runpath
to the Open MPI configury line.
Fixes#1089
Signed-off-by: Howard Pritchard <howardp@lanl.gov>
Per discussion at last developer's forum, platforms
not actively being tested (either in Jenkins or
at least weekly in MTT) are not eligible to be listed
as supported platforms. Move a number of systems out
of the supported list.
Signed-off-by: Brian Barrett <bbarrett@amazon.com>
Remove loadleveler as it is obsolescent and is no longer supported.
Fixes#3167
We'll wait for final check of whether or not loadleveler even
compiles/functions before merging this.
Signed-off-by: Howard Pritchard <howardp@lanl.gov>
The README on master had grown very, very stale. This commit copies
the README from the tip of the v2.x branch (from
https://github.com/open-mpi/ompi/pull/3119) and preserves a few minor
differences between master and the v2.x branch.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
[skip ci]
bot:notest
Add more clarifying statements about our definition of "backwards
compatibility" -- adding an example with static linking and another
with containers.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
Also update the configure.ac help message for --enable-mca-no-build to
avoid using a framework name that does not exist any more.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
* Add a configure time option to rename libmpi(_FOO).*
- `--with-libmpi-name=STRING`
* This commit only impacts the installed libraries.
Internal, temporary libraries have not been renamed to limit the
scope of the patch to only what is needed.
For example:
```shell
shell$ ./configure --with-libmpi-name=wookie
...
shell$ find . -name "libmpi*"
shell$ find . -name "libwookie*"
./lib/libwookie.so.0.0.0
./lib/libwookie.so.0
./lib/libwookie.so
./lib/libwookie.la
./lib/libwookie_mpifh.so.0.0.0
./lib/libwookie_mpifh.so.0
./lib/libwookie_mpifh.so
./lib/libwookie_mpifh.la
./lib/libwookie_usempi.so.0.0.0
./lib/libwookie_usempi.so.0
./lib/libwookie_usempi.so
./lib/libwookie_usempi.la
shell$
```
This component is a workaround to a bug in libibverbs that prints a
dire warning that usNIC devices are not supported (of course not --
usNIC devices provide functionality through libfabric, not
libibverbs). This component was written before a better workaround
was created: a "no op" libibverbs plugin for usNIC devices
(https://github.com/cisco/libusnic_verbs, and is also available in
binary form on cisco.com).
Hence, this component no longer builds by default. It's still
available if a user specifically asks for it (e.g., if they do not
want to install the "no op" libibverbs plugin), but it's not the
default. This component also has the side-effect of making
libopen-pal.so depend on libibverbs.so, which can be annoying for
packagers (which is another reason it isn't built by default any
more).
at Inria Bordeaux. This allows us to take advantage of the remap
capability of MPI to rearrange the ranks beased on the weights
povided by the application.
Fix the indentation and protect with __DEBUG__ one fprintf.
Add the Cecill-B license to the imported library.
Fix a compiler warning.
Restrict the TreeMatch dependencies.
The TreeMatch software is released under BSD3 (as indicated by their
copyright information @
https://gforge.inria.fr/scm/viewvc.php/COPYING?view=markup&root=treematch).
Update the README.
