Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • SWIFTsim SWIFTsim
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • SWIFT
  • SWIFTsimSWIFTsim
  • Issues
  • #277
Closed
Open
Created Mar 14, 2017 by Matthieu Schaller@matthieuOwner

Enable MPI even if MPIRUN not in $PATH

When configuring on Cray systems, there is no way to access the mpirun command. It does simply not exist on the login nodes, only on the back-end and not even in a normal form.

At the moment, if we can't run mpirun at the configure time to figure out what MPI version we are running and what level of threading support we have, we simply switch off the support of MPI. Could we avoid that and just trust the user knows what they are doing ? i.e. if MPI has been found but we can't find any form of mpirun, just keep going and leave the variables as they are ?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking