Ralph Castain 63f619f871 Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.

2014-10-10 11:39:08 -07:00

..

pmix

Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.

2014-10-10 11:39:08 -07:00

help-orted.txt

Okay, since a certain other RM out there made a fuss about being able to lock their daemons to specified cores, offer the same option here. The MCA param orte_daemon_cores can be used to specify which core(s) you want the orte daemons to use. This will have no bearing on the application procs - unbound will remain unbound, and binding directives will be applied to the apps.

2014-01-30 23:50:14 +00:00

Makefile.am

Provide a mechanism by which an upstream project can rename the OPAL and ORTE libraries. This is required by projects such as ORCM that have their own ORTE and OPAL libraries in order to avoid library confusion. By renaming their version of the libraries, the OMPI applications can correctly dynamically load the correct one for their build.

2014-10-10 11:39:08 -07:00

orted_comm.c

Per the PMIx RFC:

2014-08-21 18:56:47 +00:00

orted_main.c

Per the PMIx RFC:

2014-08-21 18:56:47 +00:00

orted.h

Remove stale code - message arrival time doesn't really mean much anymore.

2013-01-24 23:02:02 +00:00