Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
user-meso:quickstart [2014/09/18 15:18] ytang |
user-meso:quickstart [2015/03/17 02:39] ytang [Compiling the Source] |
||
---|---|---|---|
Line 26: | Line 26: | ||
* A MPI compiler, e.g. OpenMPI or MPICH. | * A MPI compiler, e.g. OpenMPI or MPICH. | ||
* CUDA Toolkit | * CUDA Toolkit | ||
- | |||
=== Compilation === | === Compilation === | ||
+ | |||
+ | Short version: | ||
<code bash> | <code bash> | ||
- | cd USER-MESO | + | $ cd USER-MESO |
- | make clean-all # delete temporary files if any was left from last compilation | + | $ make clean-all # delete temporary files if any was left from last compilation |
- | make yes-molecule # dependency | + | $ make yes-molecule # dependency |
- | make yes-user-meso # configure the USER-MESO package | + | $ make yes-user-meso # configure the USER-MESO package |
- | make meso | + | $ make meso |
</code> | </code> | ||
+ | Long Version: | ||
+ | First, make sure that mpic++ and nvcc are available by | ||
+ | <code bash> | ||
+ | $ which mpic++ | ||
+ | $ which nvcc | ||
+ | </code> | ||
+ | You should be expecting output that looks like | ||
+ | <code bash> | ||
+ | $ which mpic++ | ||
+ | /usr/lib64/mpich/bin/mpic++ | ||
+ | $ which nvcc | ||
+ | /usr/local/cuda/bin/nvcc | ||
+ | </code> | ||
+ | If you are sure that MPI and CUDA are present, but still get messages like | ||
+ | <code bash> | ||
+ | /usr/bin/which: no mpic++ in (/usr/local/bin:/bin:/usr/bin) | ||
+ | </code> | ||
+ | Then adjust **''Makefile.meso''** located in **''USER-MESO/MAKE''** by setting the **''CC''** and **''MPICXX''** environment variables to be the absolute path to nvcc and mpic++, respectively. | ||
---- | ---- |