Difference between revisions of "CamCASP/Compilation"

From CUC3
Jump to navigation Jump to search
import>Am592
 
import>Ajs1
m
Line 40: Line 40:
 
</pre>
 
</pre>
   
These are really simple scripts. After compilation (when '''makeall''' exits) the default GCC flags will be set. So your experimental version of GCC doesn't effect any thing else.
+
These are really simple scripts. After compilation (when '''makeall''' exits) the default GCC flags will be set. So your experimental version of GCC doesn't affect any thing else.

Revision as of 08:09, 25 December 2008

CamCASP => Compilation

Notes on compiling CamCASP

  • Gfortran

There seem to be problems with gfortran versions earlier than 4.3. I think it is because the preprocessor is not automatically used (even if -cpp is used, because only with version 4.4 is this option recognised). It may be possible to get around this, but for now, I've found it easier to download my own copy of GCC 4.4.

GCC 4.4 will reside in its own directory. Do not install it in with the other GCC compilers as it is still under development. Because it will reside in a non-standard location, you need to set some environment scripts to get the compilation going. I use the following scripts.

1. gcc_4.4.env

#!/bin/bash

gcc44="tmp/gcc-trunk"
export LD_RUN_PATH=${HOME}/$gcc44/lib64
echo $LD_RUN_PATH
export LD_LIBRARY_PATH=${HOME}/$gcc44/lib64:$LD_LIBRARY_PATH
export PATH=${HOME}/$gcc44/bin:$PATH

2. makeall

#!/bin/bash
source ./gcc_4.4.env
echo $LD_RUN_PATH
echo $LD_LIBRARY_PATH
gfortran -v

mymake='make COMPILER=gfortran MACHINE=tati '

${mymake} NAME=camcasp    clean

${mymake} NAME=camcasp
${mymake} NAME=cluster
${mymake} NAME=process
${mymake} NAME=pfit
${mymake} NAME=casimir

exit

These are really simple scripts. After compilation (when makeall exits) the default GCC flags will be set. So your experimental version of GCC doesn't affect any thing else.