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

In machine_setup.sh on macOS, prompt for MPI library path #201

Merged
merged 2 commits into from
Apr 23, 2024

Conversation

johnomotani
Copy link
Collaborator

MPIPreferences.use_system_binary() does not find the MPI library when it was installed with homebrew on macOS, so prompt for the user to give the path to the MPI library instead.

@LucasMontoya4 does this work for you?

@mabarnes did you need to work around this problem when using the machines/machine_setup.sh setup script?

Is there a default that we should check (for non-homebrew setups?) that could find the MPI library automatically? I don't have a Mac to test...

MPIPreferences.use_system_binary() does not find the MPI library when it
was installed with homebrew on macOS, so prompt for the user to give the
path to the MPI library instead.
@johnomotani johnomotani added the bug Something isn't working label Apr 11, 2024
@LucasMontoya4
Copy link
Collaborator

@johnomotani I’ll try that one out - although I’m not sure how common it is for Mac users to install MPI with homebrew, but I guess it’s still a general solution!

@johnomotani
Copy link
Collaborator Author

I've added the try-catch so if MPIPreferences.use_system_library() (with no extra arguments) runs without error, then we don't need to prompt for the MPI library path. So I think this is ready to merge now.

@johnomotani johnomotani merged commit 95cb5b1 into master Apr 23, 2024
17 checks passed
@johnomotani johnomotani deleted the mac-mpi-setup branch April 23, 2024 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants