Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inaccurate documentation tips_and_tricks #806

Closed
DebRez opened this issue Mar 1, 2019 · 2 comments
Closed

Inaccurate documentation tips_and_tricks #806

DebRez opened this issue Mar 1, 2019 · 2 comments

Comments

@DebRez
Copy link
Contributor

DebRez commented Mar 1, 2019

https://open-mpi.github.io/mtt/pages/tips_and_tricks.html

The Compiler Configuration section is all perl based stuff. Need to document current way env vars are set in ini files.

Maybe we should implement something like this if we haven't already->

MPI Install Errors
Sometimes MTT finds a problem in a middleware install, but a human wants to go examine it manually. When MTT installs a middleware under its scratch tree, it will automatically drop two files – one for sh-flavored shells and one for csh-flavored shells – that set the PATH and LD_LIBRARY_PATH to get to the middleware install. The exact location of these files depends on the section names in your INI file and the exact version number of the MPI in question. Specifically, these files will be in:

/installs////mpi_installed_vars.sh
/installs////mpi_installed_vars.csh
Hence, you can source these files like this (assuming a csh-flavored shell):

shell% cd /installs///
shell% source mpi_installed_vars.csh
Mpicc, mpirun, etc. will then be in your PATH, and the appropriate libraries will be in your LD_LIBRARY_PATH. Additionally, the environment variable MPI_ROOT will be set that points to the top-level installation directory for the middlewareBuild. This is useful with Open MPI’s --prefix option to mpirun, for example. Note that all the files related to the testing of that MPI are under this tree – the source tree, the tests, etc. So you can go examine the entire test – not just put the MPI in question in your path.

@DebRez DebRez self-assigned this Mar 1, 2019
@DebRez DebRez assigned ribab and unassigned DebRez Sep 25, 2019
@hppritcha hppritcha assigned hppritcha and unassigned ribab Dec 6, 2019
@hppritcha hppritcha removed the invalid label Dec 6, 2019
hppritcha added a commit to hppritcha/mtt that referenced this issue Dec 16, 2019
Note where some of the suggested tips and tricks are only applicable to the Perl client.

Relates to open-mpi#806

Signed-off-by: Howard Pritchard <howardp@lanl.gov>
hppritcha added a commit to hppritcha/mtt that referenced this issue Dec 16, 2019
Note where some of the suggested tips and tricks are only applicable to the Perl client.

Relates to open-mpi#806

Signed-off-by: Howard Pritchard <howardp@lanl.gov>
@hppritcha
Copy link
Member

opened issue #890 to better document the enhancement request in this issue's description.

@hppritcha
Copy link
Member

closed via #888

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants