bgirgis/cpp-thirdparty
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Bassem Girgis
2018-12-20 17:34:07 -06:00
parent 7a2d899662
commit 81b4b9e273
34743 changed files with 5940233 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

61
linx64/mpi/openmpi/share/pmix/help-mca-base.txt Normal file
View File

@@ -0,0 +1,61 @@
# -*- text -*-
#
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
# University Research and Technology
# Corporation. All rights reserved.
# Copyright (c) 2004-2005 The University of Tennessee and The University
# of Tennessee Research Foundation. All rights
# reserved.
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
# University of Stuttgart. All rights reserved.
# Copyright (c) 2004-2005 The Regents of the University of California.
# All rights reserved.
# Copyright (c) 2008-2014 Cisco Systems, Inc. All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English help file for PMIX MCA error messages.
#
[find-available:not-valid]
A requested component was not found, or was unable to be opened. This
means that this component is either not installed or is unable to be
used on your system (e.g., sometimes this means that shared libraries
that the component requires are unable to be found/loaded). Note that
PMIX stopped checking at the first component that it did not find.
Host: %s
Framework: %s
Component: %s
#
[find-available:none found]
No components were able to be opened in the %s framework.
This typically means that either no components of this type were
installed, or none of the installed componnets can be loaded.
Sometimes this means that shared libraries required by these
components are unable to be found/loaded.
Host: %s
Framework: %s
#
[framework-param:too-many-negates]
MCA framework parameters can only take a single negation operator
("^"), and it must be at the beginning of the value. The following
value violates this rule:
%s
When used, the negation operator sets the "exclusive" behavior mode,
meaning that it will exclude all specified components (and implicitly
include all others). If the negation operator is not specified, the
"inclusive" mode is assumed, meaning that all specified components
will be included (and implicitly exclude all others).
For example, "^a,b" specifies the exclusive behavior and means "use
all components *except* a and b", while "c,d" specifies the inclusive
behavior and means "use *only* components c and d."
You cannot mix inclusive and exclusive behavior.

139
linx64/mpi/openmpi/share/pmix/help-mca-var.txt Normal file
View File

@@ -0,0 +1,139 @@
# -*- text -*-
#
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
# University Research and Technology
# Corporation. All rights reserved.
# Copyright (c) 2004-2005 The University of Tennessee and The University
# of Tennessee Research Foundation. All rights
# reserved.
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
# University of Stuttgart. All rights reserved.
# Copyright (c) 2004-2005 The Regents of the University of California.
# All rights reserved.
# Copyright (c) 2008-2011 Cisco Systems, Inc. All rights reserved.
# Copyright (c) 2013 Los Alamos National Security, LLC. All rights
# reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English help file for PMIX MCA error messages.
#
[invalid-flag-combination]
ERROR: An invalid combination of flags was passed to pmix_mca_base_var_register.
Variable: %s
Flags: %s %s
#
[default-only-param-set]
WARNING: A user-supplied value attempted to override the default-only MCA
variable named "%s".
The user-supplied value was ignored.
#
[missing-param-file]
Process %d Unable to locate the variable file "%s" in the following search path:
%s
#
[deprecated-mca-env]
A deprecated MCA variable value was specified in the environment or
on the command line. Deprecated MCA variables should be avoided;
they may disappear in future releases.
Deprecated variable: %s
New variable: %s
#
[deprecated-mca-cli]
A deprecated MCA variable value was specified on the command line. Deprecated
MCA variables should be avoided; they may disappear in future releases.
Deprecated variable: %s
New variable: %s
#
[deprecated-mca-file]
A deprecated MCA variable value was specified in an MCA variable
file. Deprecated MCA variables should be avoided; they may disappear
in future releases.
Deprecated variable: %s
Source file: %s
New variable: %s
#
[mutually-exclusive-vars]
Two mutually-exclusive MCA variables were specified. This can result
in undefined behavior, such as ignoring the components that the MCA
variables are supposed to affect.
1st MCA variable: %s
Source of value: %s
2nd MCA variable: %s
Source of value: %s
#
[re-register-with-different-type]
An MCA variable was re-registered with a different type (i.e., it was
either originally registered as an INT and re-registered as a STRING,
or it was originially registered as a STRING and re-registered as an
INT). This a developer error; your job may abort.
MCA variable name: %s
#
[var-name-conflict]
A name collision was detected on an MCA variable name. This can happen
if two components try to register the same variable with slightly
different name components. The conflicting variables are listed below:
MCA variable name: %s
New name: %s %s %s
Existing name: %s %s %s
#
[overridden-param-set]
WARNING: A user-supplied value attempted to set a variable that is set
in the override variable file (pmix-mca-params-override.conf).
Variable: %s
The user-supplied value was ignored.
#
[invalid-value]
An invalid value was supplied for an MCA variable.
Variable : %s
Value : %s
#
[invalid-value-enum]
An invalid value was supplied for an enum variable.
Variable : %s
Value : %s
Valid values : %s
#
[environment-only-param]
WARNING: The special MCA parameter "%s" was set in
an unexpected way, and is likely not working the way you want it to.
Specifically, this MCA parameter is "special" in that it can *only* be
set in the environment. Setting this value in a file -- and sometimes
even on the command line -- will not work as intended. The *only* way
to set this value is to set "PMIX_MCA_%s" in the environment before
starting your job.
Value: %s
Source: %s
#
[incorrect-env-list-param]
WARNING: The format of "pmix_mca_base_env_list" parameter is a delimited list of VAR=VAL or
VAR instances. By default, the delimiter is a semicolon: VAR1=VAL1;VAR2;VAR3=VAL3;...
You can set other via "pmix_mca_base_env_list_delimiter" parameter. If the delimiter is a
semicolon, the value of "pmix_mca_base_env_list" variable should be quoted to not interfere
with SHELL command line parsing. In the case where a value is not assigned to variable
VAR, the value will be taken from the current environment.
The following environment variable was not found in the environment:
Variable: %s
MCA variable value: %s
#
[incorrect-env-list-sep]
An invalid value was supplied for an MCA variable "pmix_mca_base_env_list_delimiter".
The "pmix_mca_base_env_list" variable will be ignored.
Value: %s

19
linx64/mpi/openmpi/share/pmix/help-pmix-psensor-file.txt Normal file
View File

@@ -0,0 +1,19 @@
# -*- text -*-
#
# Copyright (c) 2009 Cisco Systems, Inc. All rights reserved.
#
# Copyright (c) 2017 Intel, Inc. All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English general help file for the file sensor
#
[file-stalled]
A specified file is not changing, indicating a possibly stalled application:
File: %s
Last size: %lu
Last access: %sLast modification: %s

20
linx64/mpi/openmpi/share/pmix/help-pmix-psensor-heartbeat.txt Normal file
View File

@@ -0,0 +1,20 @@
# -*- text -*-
#
# Copyright (c) 2010 Cisco Systems, Inc. All rights reserved.
#
# Copyright (c) 2017 Intel, Inc. All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English general help file for the memory usage sensor
#
[mem-limit-exceeded]
A process has exceeded the specified limit on memory usage:
Node: %s
Process rank: %s
Memory used: %luGbytes
Memory limit: %luGbytes

70
linx64/mpi/openmpi/share/pmix/help-pmix-runtime.txt Normal file
View File

@@ -0,0 +1,70 @@
# -*- text -*-
#
# Copyright (c) 2004-2007 The Trustees of Indiana University and Indiana
# University Research and Technology
# Corporation. All rights reserved.
# Copyright (c) 2004-2005 The University of Tennessee and The University
# of Tennessee Research Foundation. All rights
# reserved.
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
# University of Stuttgart. All rights reserved.
# Copyright (c) 2004-2005 The Regents of the University of California.
# All rights reserved.
# Copyright (c) 2011 Oak Ridge National Labs. All rights reserved.
# Copyright (c) 2014 Cisco Systems, Inc. All rights reserved.
# Copyright (c) 2017-2018 Intel, Inc. All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English general help file for PMIX.
#
[pmix_init:startup:internal-failure]
It looks like pmix_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during pmix_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
PMIX developer):
%s failed
--> Returned value %d instead of PMIX_SUCCESS
#
[missingdata]
PMIx has detected that the host RM failed to provide all the job-level
information specified by the PMIx standard. This is not necessarily
a fatal situation, but may negatively impact your launch performance.
If you feel you have received this warning in error, or wish to ignore
it in the future, you can disable it by setting the PMIx MCA parameter
"pmix_suppress_missing_data_warning=1"
#
[no-plugins]
We were unable to find any usable plugins for the %s framework. This PMIx
framework requires at least one plugin in order to operate. This can be caused
by any of the following:
* we were unable to build any of the plugins due to some combination
of configure directives and available system support
* no plugin was selected due to some combination of MCA parameter
directives versus built plugins (i.e., you excluded all the plugins
that were built and/or could execute)
* the PMIX_INSTALL_PREFIX environment variable, or the MCA parameter
"mca_base_component_path", is set and doesn't point to any location
that includes at least one usable plugin for this framework.
Please check your installation and environment.
#
[ptl:message-too-large]
A message has been received that exceeds the size limit:
Message size: %lu
Size limit: %lu
The limit is enforced to protect against bad actors. If you believe that
the message was likely legitimate, then adjust the message size by
setting the ptl_base_max_msg_size MCA parameter.

38
linx64/mpi/openmpi/share/pmix/help-pmix-server.txt Normal file
View File

@@ -0,0 +1,38 @@
# -*- text -*-
#
# Copyright (c) 2016 Intel, Inc. All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
#
[rnd-path-too-long]
The PMIx server was unable to setup a rendezvous file due to your
system's restriction for Unix's socket's path-length.
Temporary directory: %s
Rendezvous filename: %s
Please try to set TMPDIR to something short (like /tmp) or change
your computer's name to something shorter (see uname -n).
[listener-failed-start]
The PMIx server was unable to setup a rendezvous point. This is
usually due to a conflicting stale named pipe from a prior failed
job, thus preventing the server from binding to its assigned socket.
Rendezvous filename: %s
Please remove the stale file and try again.
[data-store-failed]
The PMIx server was unable to store the specified key-value:
Key: %s
The precise reason for the failure was provided in the above
"error-log" message. This is probably something that should
be referred to the PMIx developers.
[listener-thread-start]
The PMIx server's listener thread failed to start. We cannot
continue.

48
linx64/mpi/openmpi/share/pmix/pmix-valgrind.supp Normal file
View File

@@ -0,0 +1,48 @@
# -*- text -*-
#
# Copyright (c) 2015 Intel, Inc. All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
{
fin1
Memcheck:Leak
fun:malloc
fun:evthread_posix_lock_alloc
fun:evutil_secure_rng_global_setup_locks_
fun:event_global_setup_locks_
fun:evthread_use_pthreads
fun:pmix_start_progress_thread
fun:PMIx_server_init
fun:main
}
{
fin2
Memcheck:Leak
fun:malloc
fun:evthread_posix_lock_alloc
fun:evsig_global_setup_locks_
fun:event_global_setup_locks_
fun:evthread_use_pthreads
fun:pmix_start_progress_thread
fun:PMIx_Init
fun:main
}
{
fin3
Memcheck:Leak
fun:malloc
fun:evthread_posix_lock_alloc
fun:evutil_secure_rng_global_setup_locks_
fun:event_global_setup_locks_
fun:evthread_use_pthreads
fun:pmix_start_progress_thread
fun:PMIx_init
fun:main
}