Building Git Baselibs: Difference between revisions
| (One intermediate revision by the same user not shown) | |||
| Line 26: | Line 26: | ||
4) lib/mkl-18.0.5.274 | 4) lib/mkl-18.0.5.274 | ||
5) other/python/GEOSpyD/Ana2018.12_py2.7 | 5) other/python/GEOSpyD/Ana2018.12_py2.7 | ||
6) other/git-2.11.0 | |||
7) other/cmake-3.8.2 | |||
Or for copy/paste: | |||
$ module purge | |||
$ module load other/comp/gcc-6.3 comp/intel-18.0.5.274 mpi/impi-18.0.5.274 lib/mkl-18.0.5.274 other/python/GEOSpyD/Ana2018.12_py2.7 other/git-2.11.0 other/cmake-3.8.2 | |||
'''Note''': It's a good idea to build Baselibs in a clean environment. If you have cruft in, say, <tt>LD_LIBRARY_PATH</tt>, it's possible the build will not pick up the libraries you expect. | '''Note''': It's a good idea to build Baselibs in a clean environment. If you have cruft in, say, <tt>LD_LIBRARY_PATH</tt>, it's possible the build will not pick up the libraries you expect. | ||
| Line 38: | Line 43: | ||
Some modules set these and most of the Baselibs assume the C-preprocessor will be gcc, not, say, pgcpp (which is '''not''' a C++ compiler!). | Some modules set these and most of the Baselibs assume the C-preprocessor will be gcc, not, say, pgcpp (which is '''not''' a C++ compiler!). | ||
=== DISCOVER: Add to PATH === | |||
NOTE: On discover, because SLES11 is so old, you'll need newer basic utilities to build Baselibs. To do this: | |||
$ setenv PATH /discover/swdev/mathomp4/bin:$PATH | |||
(or the bash export equivalent) | |||
=== Build Environment Settings === | === Build Environment Settings === | ||