Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
user-meso:quickstart [2014/09/18 15:33] ytang |
user-meso:quickstart [2015/03/17 02:40] (current) ytang [Troubleshooting] |
||
---|---|---|---|
Line 21: | Line 21: | ||
---- | ---- | ||
- | ==== Compiling the Source ==== | + | ==== Compilation ==== |
=== Prerequisites === | === Prerequisites === | ||
Line 41: | Line 41: | ||
Long Version: | Long Version: | ||
- | First, make sure that mpic++ and nvcc are in the system path by | + | First, make sure that mpic++ and nvcc are available by |
<code bash> | <code bash> | ||
$ which mpic++ | $ which mpic++ | ||
Line 53: | Line 53: | ||
/usr/local/cuda/bin/nvcc | /usr/local/cuda/bin/nvcc | ||
</code> | </code> | ||
- | If you got something like | + | If you are sure that MPI and CUDA are present, but still get messages like |
<code bash> | <code bash> | ||
/usr/bin/which: no mpic++ in (/usr/local/bin:/bin:/usr/bin) | /usr/bin/which: no mpic++ in (/usr/local/bin:/bin:/usr/bin) | ||
</code> | </code> | ||
- | Then you need to adjust **''Makefile.meso''** located in **''USER-MESO/MAKE''** accordingly: | + | 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. |
- | - replace of mpic++ with the full path that points to the MPI compiler | + | |
- | - replace nvcc with the full path that point | + | |
- | + | ||
- | <code bash> | + | |
- | $ cd USER-MESO | + | |
- | $ make clean-all # delete temporary files if any was left from last compilation | + | |
- | $ make yes-molecule # dependency | + | |
- | $ make yes-user-meso # configure the USER-MESO package | + | |
- | $ make meso | + | |
- | </code> | + | |
---- | ---- | ||
- | ==== Troubleshooting ==== | ||
- | ---- | ||
==== Creating Input Script ==== | ==== Creating Input Script ==== |