From Earlham Cluster Department
Revision as of 16:58, 5 October 2009 by Kay
Software build options
ARCHPATH=`uname -s`/`/cluster/software/os_release`/`uname -p`
./configure --prefix=/cluster/software/modules-sw/tcl/8.5.7/$ARCHPATH --enable-shared && make
./configure --prefix=/cluster/software/modules-sw/modules/3.2.7/$ARCHPATH --with-tcl=/cluster/software/modules-sw/tcl/8.5.7/$ARCHPATH/lib --with-static=yes && make
- Had to remove bash_completion from init/Makefile.
- After installation, changed the version from 3.2.6->3.2.7 in the init directory, and /usr/share/Modules to /cluster/software/modules-sw/modules/3.2.7/$ARCHPATH/Modules
./configure --prefix=/cluster/software/modules-sw/openmpi/1.3.1/$ARCHPATH && make
That's still doable with multiple modules repositories. We can setup meta-modules that don't actually point you at software but alter how modules itself behaves. The master meta-module would prepend MODULEPATH with (say) "/cluster/software/modules" for software that's the same across all the clusters, and modules-bobsced would prepend MODULEPATH with "/cluster/bobsced/software/modules". Just like with PATH, the first hit within a module repository is used. If Perl is only in the master software repository it'll be grabbed from there, but if OpenMPI is in both it'll be grabbed from the bobsced repository since it comes before the master repository.
. /cluster/software/modules.shgets it working
/cluster/software/modulesis where the actual configuration files for each module (ie each piece of software) is stored in text files
/cluster/software/modules-swis where the common source code gets installed to (not bobsced-specific)