liinux编译好的openmpi库

# -*- text -*- # # Copyright (c) 2004-2006 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) 2007-2016 Cisco Systems, Inc. All rights reserved. # Copyright (c) 2012 Oak Ridge National Labs. 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 Open RTE's orterun. # [orterun:init-failure] Open RTE was unable to initialize properly. The error occured while attempting to %s. Returned value %d instead of ORTE_SUCCESS. [orterun:usage] %s (%s) %s Usage: %s [OPTION]... [PROGRAM]... Start the given program using Open RTE %s Report bugs to %s [orterun:version] %s (%s) %s Report bugs to %s [orterun:allocate-resources] %s was unable to allocate enough resources to start your application. This might be a transient error (too many nodes in the cluster were unavailable at the time of the request) or a permenant error (you requsted more nodes than exist in your cluster). While probably only useful to Open RTE developers, the error returned was %d. [orterun:error-spawning] %s was unable to start the specified application. An attempt has been made to clean up all processes that did start. The error returned was %d. [orterun:appfile-not-found] Unable to open the appfile: %s Double check that this file exists and is readable. [orterun:executable-not-specified] No executable was specified on the %s command line. Aborting. [orterun:multi-apps-and-zero-np] %s found multiple applications specified on the command line, with at least one that failed to specify the number of processes to execute. When specifying multiple applications, you must specify how many processes of each to launch via the -np argument. [orterun:nothing-to-do] %s could not find anything to do. It is possible that you forgot to specify how many processes to run via the "-np" argument. [orterun:call-failed] %s encountered a %s call failure. This should not happen, and usually indicates an error within the operating system itself. Specifically, the following error occurred: %s The only other available information that may be helpful is the errno that was returned: %d. [orterun:environ] %s was unable to set %s = %s in the environment. Returned value %d instead of ORTE_SUCCESS. [orterun:precondition] %s was unable to precondition transports Returned value %d instead of ORTE_SUCCESS. [orterun:attr-failed] %s was unable to define an attribute Returned value %d instead of ORTE_SUCCESS. # [orterun:proc-ordered-abort] %s has exited due to process rank %lu with PID %lu on node %s calling "abort". This may have caused other processes in the application to be terminated by signals sent by %s (as reported here). # [orterun:proc-exit-no-sync] %s has exited due to process rank %lu with PID %lu on node %s exiting improperly. There are three reasons this could occur: 1. this process did not call "init" before exiting, but others in the job did. This can cause a job to hang indefinitely while it waits for all processes to call "init". By rule, if one process calls "init", then ALL processes must call "init" prior to termination. 2. this process called "init", but exited without calling "finalize". By rule, all processes that call "init" MUST call "finalize" prior to exiting or it will be considered an "abnormal termination" 3. this process called "MPI_Abort" or "orte_abort" and the mca parameter orte_create_session_dirs is set to false. In this case, the run-time cannot detect that the abort call was an abnormal termination. Hence, the only error message you will receive is this one. This may have caused other processes in the application to be terminated by signals sent by %s (as reported here). You can avoid this message by specifying -quiet on the %s command line. # [orterun:proc-exit-no-sync-unknown] %s has exited due to a process exiting without calling "finalize", but has no info as to the process that caused that situation. This may have caused other processes in the application to be terminated by signals sent by %s (as reported here). # [orterun:proc-aborted] %s noticed that process rank %lu with PID %lu on node %s exited on signal %d. # [orterun:proc-aborted-unknown] %s noticed that the job aborted, but has no info as to the process that caused that situation. # [orterun:proc-aborted-signal-unknown] %s noticed that the job aborted by signal, but has no info as to the process that caused that situation. # [orterun:proc-aborted-strsignal] %s noticed that process rank %lu with PID %lu on node %s exited on signal %d (%s). # [orterun:abnormal-exit] WARNING: %s has exited before it received notification that all started processes had terminated. You should double check and ensure that there are no runaway processes still executing. # [orterun:sigint-while-processing] WARNING: %s is in the process of killing a job, but has detected an interruption (probably control-C). It is dangerous to interrupt %s while it is killing a job (proper termination may not be guaranteed). Hit control-C again within 1 second if you really want to kill %s immediately. # [orterun:double-prefix] Both a prefix was supplied to %s and the absolute path to %s was given: Prefix: %s Path: %s Only one should be specified to avoid potential version confusion. Operation will continue, but the -prefix option will be used. This is done to allow you to select a different prefix for the backend computation nodes than used on the frontend for %s. # [orterun:app-prefix-conflict] Both a prefix or absolute path was given for %s, and a different prefix provided for the first app_context: Mpirun prefix: %s App prefix: %s Only one should be specified to avoid potential version confusion. Operation will continue, but the application's prefix option will be ignored. # [orterun:empty-prefix] A prefix was supplied to %s that only contained slashes. This is a fatal error; %s will now abort. No processes were launched. # [debugger-mca-param-not-found] Internal error -- the orte_base_user_debugger MCA parameter was not able to be found. Please contact the Open RTE developers; this should not happen. # [debugger-orte_base_user_debugger-empty] The MCA parameter "orte_base_user_debugger" was empty, indicating that no user-level debuggers have been defined. Please set this MCA parameter to a value and try again. # [debugger-not-found] A suitable debugger could not be found in your PATH. Check the values specified in the orte_base_user_debugger MCA parameter for the list of debuggers that was searched. # [debugger-exec-failed] %s was unable to launch the specified debugger. This is what was launched: %s Things to check: - Ensure that the debugger is installed properly - Ensure that the "%s" executable is in your path - Ensure that any required licenses are available to run the debugger # [orterun:sys-limit-pipe] %s was unable to launch the specified application as it encountered an error: Error: system limit exceeded on number of pipes that can be open Node: %s when attempting to start process rank %lu. This can be resolved by setting the mca parameter opal_set_max_sys_limits to 1, increasing your limit descriptor setting (using limit or ulimit commands), asking the system administrator for that node to increase the system limit, or by rearranging your processes to place fewer of them