Building CVS Baselibs: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This page will detail the process of building Baselibs. For the purposes of this page, <tt>GMAO-Baselibs-4_0_7</tt> as an example tag, but this process should work with any tag after <tt>GMAO-Baselibs-3_3_0</tt>. | This page will detail the process of building Baselibs. For the purposes of this page, <tt>GMAO-Baselibs-4_0_7</tt> as an example tag, but this process should work with any tag after <tt>GMAO-Baselibs-3_3_0</tt>. | ||
NOTE: This is now outdated as Baselibs has moved to GitHub. | |||
== Obtaining Baselibs == | |||
=== Set up the 'bcvs' alias === | === Check out Baselibs === | ||
The first step is to check out the tag you want. Tags on CVS are versions of Baselibs 2.x.y, 3.x.y, and 4.x.y. For version 5.x.y, the recommended Baselibs is now hosted on NASA Internal Github and build instructions can be found on [[Building_Git_Baselibs|the Building Git Baselibs page]]. | |||
==== Set up the 'bcvs' alias ==== | |||
Something useful to set up first is an alias that you can use to refer to the CVS repo for Baselibs. This is because the Baselibs are hosted on progress while the GEOS-5 model and most other tools are on the CVSACL repo. So, I recommend setting a 'bcvs' alias: | Something useful to set up first is an alias that you can use to refer to the CVS repo for Baselibs. This is because the Baselibs are hosted on progress while the GEOS-5 model and most other tools are on the CVSACL repo. So, I recommend setting a 'bcvs' alias: | ||
| Line 13: | Line 17: | ||
where <tt>USERNAME</tt> is your username ''at progress''. Note that this works on discover and pleiades, but elsewhere you'll need to set up a tunnel to progress and alter the CVSROOT appropriately. | where <tt>USERNAME</tt> is your username ''at progress''. Note that this works on discover and pleiades, but elsewhere you'll need to set up a tunnel to progress and alter the CVSROOT appropriately. | ||
=== Checking out the tag === | ==== Checking out the tag ==== | ||
Next, checkout the tag: | Next, checkout the tag: | ||
| Line 51: | Line 55: | ||
=== (OPTIONAL) Set MPICC_CC and MPICXX_CXX variables if using MPT === | === (OPTIONAL) Set MPICC_CC and MPICXX_CXX variables if using MPT === | ||
If you are using MPT | If you are using SGI MPT, and you wish to use, say, the PGI C and C++ compilers instead of GNU, you must set the MPICC_CC and MPICXX_CXX variables to be the "correct" compilers. This can be done either in the environment full (beware!) or during the install by adding at the end: | ||
MPICC_CC=pgcc MPICXX_CXX=pgc++ | |||
MPICC_CC=pgcc MPICXX_CXX= | |||
=== Build and install === | === Build and install === | ||
| Line 93: | Line 96: | ||
-------+---------+---------+-------------- | -------+---------+---------+-------------- | ||
Note that this is not as comprehensive as looking at the log file as it is possible that some submakes will fail but not communicate that well enough to the main make process. | Note that this is not as comprehensive as looking at the log file as it is possible that some submakes will fail but not communicate that well enough to the main make process. Test | ||
== Checking Baselibs == | == Checking Baselibs == | ||
| Line 102: | Line 105: | ||
Note that at the moment, many will exit with errors. For example, NetCDF has tests that require internet access and if a check is done on a compute node with no external access, it will fail. | Note that at the moment, many will exit with errors. For example, NetCDF has tests that require internet access and if a check is done on a compute node with no external access, it will fail. | ||
[[Category:Baselibs]] | [[Category:Baselibs]] | ||
[[Category:SI Team]] | [[Category:SI Team]] | ||