Difference between revisions of "Installation/Linux/OpenFOAM-2.1.1/CentOS SL RHEL"

From OpenFOAMWiki
(CentOS 5.8: added options to makeParaView for forcing it to copy Qt library files. Create symbolic link, for forcing hook-up to qmake's location.)
(Now using the template for accessing the user guide)
 
(26 intermediate revisions by the same user not shown)
Line 7: Line 7:
 
In '''theory''', all of the above follow the same versioning. Therefore, at the time this page was first written, RHEL, CentOS and SL were all at version {{tt|6.3}}.
 
In '''theory''', all of the above follow the same versioning. Therefore, at the time this page was first written, RHEL, CentOS and SL were all at version {{tt|6.3}}.
  
Both SL and CentOS derive from RHEL, but [http://sourceforge.net/apps/mediawiki/centfoam/index.php?title=Main_Page CentFOAM] is what inspired this page. Therefore, before even trying to follow the instructions on this page, try first [http://sourceforge.net/apps/mediawiki/centfoam/index.php?title=Main_Page CentFOAM].
+
Both SL and CentOS derive from RHEL, but [http://centfoam.sourceforge.net/wiki/index.php/Main_Page CentFOAM] is what inspired this page. Therefore, before even trying to follow the instructions on this page, try first [http://centfoam.sourceforge.net/wiki/index.php/Main_Page CentFOAM].
  
 
Last but not least, RHEL uses Fedora as their bleeding edge Linux Distribution, where they test new features. This leads to very close similarities between them, e.g. RHEL 6.3 is very similar to Fedora 14; which means that whatever you can build on Fedora 14, you should also be able to build on RHEL 6.3!
 
Last but not least, RHEL uses Fedora as their bleeding edge Linux Distribution, where they test new features. This leads to very close similarities between them, e.g. RHEL 6.3 is very similar to Fedora 14; which means that whatever you can build on Fedora 14, you should also be able to build on RHEL 6.3!
Line 23: Line 23:
 
# One wrong character is enough for breaking this guide, so make sure you can read the characters properly or that the installed language system does not break the copied characters!
 
# One wrong character is enough for breaking this guide, so make sure you can read the characters properly or that the installed language system does not break the copied characters!
  
== CentOS 5.8 ==
+
<br>
Note: this was tested with the normal DVD of CentOS 5.8, installed in a virtual machine.
+
  
'''Discussion thread where you can ask questions about these steps''': ''none assigned yet''
+
== CentOS 5.1 ==
 +
Note: this was tested with the normal 7 CD-pack of CentOS 5.1 x86_64, installed in a virtual machine.
  
'''THESE INSTRUCTIONS for CentOS 5.8 ARE BEING TESTED AND REVISED AT THIS MOMENT...'''
+
'''Discussion thread where you can ask questions about these steps''': [http://www.cfd-online.com/Forums/openfoam-installation/112715-problem-installation-openfoam-2-1-x-red-hat.html problem in installation in OpenFOAM-2.1.x on Red Hat]
  
 
Steps:
 
Steps:
Line 36: Line 36:
 
yum groupinstall 'Development Tools'  
 
yum groupinstall 'Development Tools'  
 
yum install gcc44 gcc44-c++ openmpi openmpi-devel zlib-devel
 
yum install gcc44 gcc44-c++ openmpi openmpi-devel zlib-devel
 +
 +
#these are needed for Qt and ParaView
 +
yum install libXt-devel libXext-devel libXrender-devel
  
 
#This one is useful, but not crucial
 
#This one is useful, but not crucial
 
yum upgrade</bash></li>
 
yum upgrade</bash></li>
 +
<li>Continue in step #2 in the section [[#CentOS 5.8|CentOS 5.8]].</li>
 +
</ol>
 +
<br>
 +
 +
== CentOS 5.8 ==
 +
Note: this was tested with the normal DVD of CentOS 5.8, installed in a virtual machine.
 +
 +
'''Discussion thread where you can ask questions about these steps''': [http://www.cfd-online.com/Forums/openfoam-installation/107980-installing-openfoam-2-1-1-centos-5-x.html Installing OpenFOAM 2.1.1 on CentOS 5.x]
 +
 +
Steps:
 +
<ol>
 +
{{Installation/Linux/SwitchToRoot}}
 +
 +
<li>Install the necessary packages:
 +
<bash>yum groupinstall 'Development Tools'
 +
yum install gcc44 gcc44-c++ openmpi openmpi-devel zlib-devel
 +
 +
#This one is useful, but not crucial
 +
yum upgrade</bash>
 +
</li>
 +
 
<li>For building OpenFOAM itself and using the dedicated Open-MPI version, it depends on whether you have installed the i386 or x86_64 architecture of CentOS/SL/RHEL. To check this, run:
 
<li>For building OpenFOAM itself and using the dedicated Open-MPI version, it depends on whether you have installed the i386 or x86_64 architecture of CentOS/SL/RHEL. To check this, run:
 
<bash>uname -m</bash>
 
<bash>uname -m</bash>
 
Now, accordingly:
 
Now, accordingly:
<ul>
+
<ul {{NoIndentStyle}}>
 
<li>For i386:
 
<li>For i386:
 
<bash>#forcefully load Open-MPI into the environment
 
<bash>#forcefully load Open-MPI into the environment
Line 53: Line 77:
 
</ul>
 
</ul>
 
</li>
 
</li>
<li>Now exit root mode:
+
 
<bash>exit</bash></li>
+
{{Installation/Linux/ExitRoot}}
 +
 
 
<li>Start a new terminal. This is because you'll need a fully refreshed shell.</li>
 
<li>Start a new terminal. This is because you'll need a fully refreshed shell.</li>
 
<li>Download and unpack (here you can copy-paste all in single go):
 
<li>Download and unpack (here you can copy-paste all in single go):
Line 64: Line 89:
 
wget "http://downloads.sourceforge.net/foam/ThirdParty-2.1.1.tgz?use_mirror=mesh" -O ThirdParty-2.1.1.tgz
 
wget "http://downloads.sourceforge.net/foam/ThirdParty-2.1.1.tgz?use_mirror=mesh" -O ThirdParty-2.1.1.tgz
  
tar xzf OpenFOAM-2.1.1.tgz  
+
tar -xzf OpenFOAM-2.1.1.tgz  
tar xzf ThirdParty-2.1.1.tgz  
+
tar -xzf ThirdParty-2.1.1.tgz  
 
</bash></li>
 
</bash></li>
 
<li>According to the previously determined architecture:
 
<li>According to the previously determined architecture:
<ul>
+
<ul {{NoIndentStyle}}>
 
<li>For i386:
 
<li>For i386:
 
<bash>#here you can change 4 to the number of cores you've got
 
<bash>#here you can change 4 to the number of cores you've got
Line 74: Line 99:
 
export WM_CC='gcc44'
 
export WM_CC='gcc44'
 
export WM_CXX='g++44'
 
export WM_CXX='g++44'
 
echo "source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS" >> $HOME/.bashrc
 
echo "export WM_CC='gcc44'; export WM_CXX='g++44'" >> $HOME/.bashrc
 
  
 
sed -i -e 's=gcc=$(WM_CC)=' OpenFOAM-2.1.1/wmake/rules/linuxGcc44/c
 
sed -i -e 's=gcc=$(WM_CC)=' OpenFOAM-2.1.1/wmake/rules/linuxGcc44/c
Line 87: Line 109:
 
export WM_CXX='g++44'
 
export WM_CXX='g++44'
 
   
 
   
echo "source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS" >> $HOME/.bashrc
+
sed -i -e 's=gcc=$(WM_CC)=' OpenFOAM-2.1.1/wmake/rules/linux64Gcc44/c
echo "export WM_CC='gcc44'; export WM_CXX='g++44'" >> $HOME/.bashrc
+
sed -i -e 's=g++=$(WM_CXX)=' OpenFOAM-2.1.1/wmake/rules/linux64Gcc44/c++</bash>
 
+
sed 's=gcc=$(WM_CC)=' OpenFOAM-2.1.1/wmake/rules/linux64Gcc44/c
+
sed 's=g++=$(WM_CXX)=' OpenFOAM-2.1.1/wmake/rules/linux64Gcc44/c++</bash>
+
 
</li>
 
</li>
 
</ul>
 
</ul>
 
</li>
 
</li>
 +
 +
<li>Save an ''alias'' in the personal {{tt|.bashrc}} file, simply by running the following commands:
 +
<bash>FULL_SETTINGS="$FOAM_SETTINGS; export WM_CC=gcc44; export WM_CXX=g++44"
 +
echo "alias of211='source \$HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc ${FULL_SETTINGS}'" >> $HOME/.bashrc
 +
unset FULL_SETTINGS
 +
</bash>
 +
{{Installation/Linux/AliasNote|OpenFOAM 2.1.1|of211}}
 +
</li>
 +
 
<li>Now let's build OpenFOAM:<br>
 
<li>Now let's build OpenFOAM:<br>
 
('''Warning''': this may take somewhere from 30 minutes to 6 hours, depending on your machine.)<br>
 
('''Warning''': this may take somewhere from 30 minutes to 6 hours, depending on your machine.)<br>
Line 101: Line 129:
  
 
# This next command will take a while... somewhere between 30 minutes to 3-6 hours.
 
# This next command will take a while... somewhere between 30 minutes to 3-6 hours.
./Allwmake > make.log 2>&1
+
./Allwmake > log.make 2>&1
  
 
#Run it a second time for getting a summary of the installation
 
#Run it a second time for getting a summary of the installation
./Allwmake > make.log 2>&1
+
./Allwmake > log.make 2>&1
 
</bash></li>
 
</bash></li>
  
<li>To check if everything went well:
+
<li>{{Installation/Linux/CheckIfAllWentWell}}</li>
<bash>#Check if icoFoam is working
+
icoFoam -help
+
 
+
#Edit the file "make.log" and check if there are any error messages
+
#Example:
+
gedit make.log
+
 
+
#Create a tarball in case you've seen any errors (it's the first error that matters)
+
#or if you don't understand the output
+
#and attach the file "make.log.tar.gz" to a post in the designated thread
+
tar -czf make.log.tar.gz make.log
+
</bash></li>
+
  
 
<li>CentOS 5.8 comes with CMake 2.6.4, but ParaView 3.12.0 needs a one of the versions from the more recent CMake 2.8.x series. Therefore, we'll need to do a custom build:
 
<li>CentOS 5.8 comes with CMake 2.6.4, but ParaView 3.12.0 needs a one of the versions from the more recent CMake 2.8.x series. Therefore, we'll need to do a custom build:
 
<bash>cd $WM_THIRD_PARTY_DIR
 
<bash>cd $WM_THIRD_PARTY_DIR
wget "http://www.openfoam.org/mantisbt/file_download.php?file_id=143&type=bug" -O getCmake
+
wget "https://raw.github.com/wyldckat/scripts4OpenFOAM3rdParty/master/getCmake"
 
chmod +x getCmake
 
chmod +x getCmake
 
./getCmake
 
./getCmake
Line 130: Line 146:
 
</bash></li>
 
</bash></li>
  
<li>CentOS 5.8 comes with Qt 4.2.1, but ParaView 3.12.0 needs at least 4.5, with 4.6 as recommended. Therefore, we'll need to do a custom build (although this will use Qt 4.7.3 by default):
+
<li>CentOS 5.8 comes with Qt 4.2.1, but ParaView 3.12.0 needs at least 4.5, with 4.6 as recommended. Therefore, we'll need to do a custom build:
 
<bash>cd $WM_THIRD_PARTY_DIR
 
<bash>cd $WM_THIRD_PARTY_DIR
wget "http://www.openfoam.org/mantisbt/file_download.php?file_id=142&type=bug" -O getQt
+
wget "https://raw.github.com/wyldckat/scripts4OpenFOAM3rdParty/master/getQt"
 
chmod +x getQt
 
chmod +x getQt
 
./getQt
 
./getQt
./makeQt
+
 
</bash></li>
+
#fix the defaults for Qt not to use gcc or g++ by default
 +
sed -i -e 's/= gcc/= gcc44/' qt-everywhere-opensource-src-4.6.4/mkspecs/common/g++.conf
 +
sed -i -e 's/= g++/= g++44/' qt-everywhere-opensource-src-4.6.4/mkspecs/common/g++.conf
 +
 +
./makeQt 4.6.4 > log.mkqt 2>&1</bash></li>
  
 
<li>Now, in order to build ParaView 3.12.0 that comes with OpenFOAM, along with the Qt version recently built:
 
<li>Now, in order to build ParaView 3.12.0 that comes with OpenFOAM, along with the Qt version recently built:
 
<bash>cd $WM_THIRD_PARTY_DIR
 
<bash>cd $WM_THIRD_PARTY_DIR
./makeParaView -qt-4.7.3 PARAVIEW_INSTALL_THIRD_PARTY_LIBRARIES:BOOL=ON
+
./makeParaView -qmake $WM_THIRD_PARTY_DIR/platforms/$WM_ARCH$WM_COMPILER/qt-4.6.4/bin/qmake PARAVIEW_INSTALL_THIRD_PARTY_LIBRARIES:BOOL=ON
ln -s platforms/linux64Gcc44/qt-4.7.3/bin/qmake platforms/linux64Gcc44/paraview-3.12.0/bin/qmake
+
  
 
cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers  
 
cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers  
 
wmSET $FOAM_SETTINGS
 
wmSET $FOAM_SETTINGS
 +
export PATH=$WM_THIRD_PARTY_DIR/platforms/$WM_ARCH$WM_COMPILER/qt-4.6.4/bin:$PATH
 
./Allwclean  
 
./Allwclean  
 
./Allwmake
 
./Allwmake
 
</bash></li>
 
</bash></li>
<li>Now you can go read the User Guide: [http://www.openfoam.org/docs/user/ official OpenFOAM User Guide]</li>
+
<li>{{Installation/ReadUserGuideEtAl_OpenFOAMFoundation}}</li>
 
</ol>
 
</ol>
  
'''Discussion thread where you can ask questions about these steps''': ''none assigned yet''
+
 
 +
{{Installation/Linux/AliasReminder|OpenFOAM 2.1.1|of211}}
 +
 
 +
 
 +
'''Discussion thread where you can ask questions about these steps''': [http://www.cfd-online.com/Forums/openfoam-installation/107980-installing-openfoam-2-1-1-centos-5-x.html Installing OpenFOAM 2.1.1 on CentOS 5.x]
 +
 
 +
<br>
  
 
== CentOS 6.3 ==
 
== CentOS 6.3 ==
Line 160: Line 186:
 
Steps:
 
Steps:
 
<ol>
 
<ol>
<li>Switch to ''root'' mode (administrator) and install the necessary packages (run one line at a time):
+
{{Installation/Linux/SwitchToRoot}}
<bash>su -
+
 
yum groupinstall 'Development Tools'  
+
<li>Install the necessary packages:
 +
<bash>yum groupinstall 'Development Tools'  
 
yum install openmpi openmpi-devel qt-devel qt-webkit-devel zlib-devel
 
yum install openmpi openmpi-devel qt-devel qt-webkit-devel zlib-devel
  
 
#This one is useful, but not crucial
 
#This one is useful, but not crucial
yum upgrade
+
yum upgrade</bash>
 +
</li>
 +
 
 +
{{Installation/Linux/ExitRoot}}
  
exit
 
</bash></li>
 
 
<li>Start a new terminal. This is because you'll need a fully refreshed shell.</li>
 
<li>Start a new terminal. This is because you'll need a fully refreshed shell.</li>
 
<li>Download and unpack (here you can copy-paste all in single go):
 
<li>Download and unpack (here you can copy-paste all in single go):
Line 179: Line 207:
 
wget "http://downloads.sourceforge.net/foam/ThirdParty-2.1.1.tgz?use_mirror=mesh" -O ThirdParty-2.1.1.tgz
 
wget "http://downloads.sourceforge.net/foam/ThirdParty-2.1.1.tgz?use_mirror=mesh" -O ThirdParty-2.1.1.tgz
  
tar xzf OpenFOAM-2.1.1.tgz  
+
tar -xzf OpenFOAM-2.1.1.tgz  
tar xzf ThirdParty-2.1.1.tgz  
+
tar -xzf ThirdParty-2.1.1.tgz  
 
</bash></li>
 
</bash></li>
 
<li>For building OpenFOAM itself, it depends on whether you have installed the i386 or x86_64 architecture of CentOS/SL/RHEL. To check this, run:
 
<li>For building OpenFOAM itself, it depends on whether you have installed the i386 or x86_64 architecture of CentOS/SL/RHEL. To check this, run:
 
<bash>uname -m</bash>
 
<bash>uname -m</bash>
 
Now, accordingly:
 
Now, accordingly:
<ul>
+
<ul {{NoIndentStyle}}>
 
<li>For i386:
 
<li>For i386:
 
<bash>#forcefully load Open-MPI into the environment
 
<bash>#forcefully load Open-MPI into the environment
Line 192: Line 220:
 
#here you can change 4 to the number of cores you've got
 
#here you can change 4 to the number of cores you've got
 
source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI WM_ARCH_OPTION=32
 
source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI WM_ARCH_OPTION=32
 
+
</bash>
echo "module load openmpi-i386" >> $HOME/.bashrc
+
Also, save an ''alias'' in the personal {{tt|.bashrc}} file, simply by running the following command:
echo "source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS" >> $HOME/.bashrc
+
<bash>echo "alias of211='module load openmpi-i386; source \$HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS'" >> $HOME/.bashrc
</bash></li>
+
</bash>
 +
{{Installation/Linux/AliasNote|OpenFOAM 2.1.1|of211}}
 +
</li>
  
 
<li>For x86_64:
 
<li>For x86_64:
Line 203: Line 233:
 
#here you can change 4 to the number of cores you've got
 
#here you can change 4 to the number of cores you've got
 
source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI
 
source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI
 
+
</bash>
echo "module load openmpi-x86_64" >> $HOME/.bashrc
+
Also, save an ''alias'' in the personal {{tt|.bashrc}} file, simply by running the following command:
echo "source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS" >> $HOME/.bashrc</bash>
+
<bash>echo "alias of211='module load openmpi-x86_64; source \$HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS'" >> $HOME/.bashrc
 +
</bash>
 +
{{Installation/Linux/AliasNote|OpenFOAM 2.1.1|of211}}
 
</li>
 
</li>
 
</ul>
 
</ul>
Line 215: Line 247:
  
 
# This next command will take a while... somewhere between 30 minutes to 3-6 hours.
 
# This next command will take a while... somewhere between 30 minutes to 3-6 hours.
./Allwmake > make.log 2>&1
+
./Allwmake > log.make 2>&1
  
 
#Run it a second time for getting a summary of the installation
 
#Run it a second time for getting a summary of the installation
./Allwmake > make.log 2>&1
+
./Allwmake > log.make 2>&1
 
</bash></li>
 
</bash></li>
  
<li>To check if everything went well:
+
<li>{{Installation/Linux/CheckIfAllWentWell}}</li>
<bash>#Check if icoFoam is working
+
icoFoam -help
+
  
#Edit the file "make.log" and check if there are any error messages
+
<li>CentOS 6.3 comes with CMake 2.6.4, but ParaView 3.12.0 needs a one of the versions from the more recent CMake 2.8.x series. Therefore, we'll need to do a custom build:
#Example:
+
<bash>cd $WM_THIRD_PARTY_DIR
gedit make.log
+
wget "https://raw.github.com/wyldckat/scripts4OpenFOAM3rdParty/master/getCmake"
 +
chmod +x getCmake
 +
./getCmake
 +
./makeCmake
 +
wmSET $FOAM_SETTINGS
 +
</bash></li>
  
#Create a tarball in case you've seen any errors (it's the first error that matters)
+
<li>Now, in order to build ParaView 3.12.0 that comes with OpenFOAM:
#or if you don't understand the output
+
<bash>cd $WM_THIRD_PARTY_DIR
#and attach the file "make.log.tar.gz" to a post in the designated thread
+
./makeParaView -qmake $(which qmake-qt4)
tar -czf make.log.tar.gz make.log
+
 
 +
#quick hack for getting qmake found on the search path
 +
ln -s $(which qmake-qt4) $WM_PROJECT_DIR/bin/qmake
 +
 
 +
cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers
 +
wmSET $FOAM_SETTINGS
 +
./Allwclean
 +
./Allwmake
 
</bash></li>
 
</bash></li>
 +
<li>{{Installation/ReadUserGuideEtAl_OpenFOAMFoundation}}</li>
 +
</ol>
 +
 +
 +
{{Installation/Linux/AliasReminder|OpenFOAM 2.1.1|of211}}
 +
 +
 +
'''Discussion thread where you can ask questions about these steps''': [http://www.cfd-online.com/Forums/openfoam-installation/107452-openfoam-installation-sl-6-3-guide-req.html#post383954 OpenFOAM installation in SL 6.3 (guide req)]
 +
 +
<br>
 +
 +
== CentOS 6.7 ==
 +
 +
'''Discussion thread where you can ask questions about these steps''': [http://www.cfd-online.com/Forums/openfoam-installation/107452-openfoam-installation-sl-6-3-guide-req.html#post383954 OpenFOAM installation in SL 6.3 (guide req)]
 +
 +
Steps:
 +
<ol>
 +
{{Installation/Linux/SwitchToRoot}}
 +
 +
<li>Install the necessary packages:
 +
<bash>yum groupinstall 'Development Tools'
 +
yum install openmpi openmpi-devel qt-devel qt-webkit-devel zlib-devel
 +
 +
#This one is useful, but not crucial
 +
yum upgrade</bash>
 +
</li>
 +
 +
{{Installation/Linux/ExitRoot}}
 +
 +
<li>Start a new terminal. This is because you'll need a fully refreshed shell.</li>
 +
<li>Download and unpack (here you can copy-paste all in single go):
 +
<bash>#OpenFOAM downloading and installation
 +
cd ~
 +
mkdir OpenFOAM
 +
cd OpenFOAM
 +
wget "http://downloads.sourceforge.net/foam/OpenFOAM-2.1.1.tgz?use_mirror=mesh" -O OpenFOAM-2.1.1.tgz
 +
wget "http://downloads.sourceforge.net/foam/ThirdParty-2.1.1.tgz?use_mirror=mesh" -O ThirdParty-2.1.1.tgz
 +
 +
tar -xzf OpenFOAM-2.1.1.tgz
 +
tar -xzf ThirdParty-2.1.1.tgz
 +
</bash></li>
 +
<li>For building OpenFOAM itself, it depends on whether you have installed the i386 or x86_64 architecture of CentOS/SL/RHEL. To check this, run:
 +
<bash>uname -m</bash>
 +
Now, accordingly:
 +
<ul {{NoIndentStyle}}>
 +
<li>For i386:
 +
<bash>#forcefully load Open-MPI into the environment
 +
module load openmpi-i386
 +
 +
#here you can change 4 to the number of cores you've got
 +
source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI WM_ARCH_OPTION=32
 +
</bash>
 +
Also, save an ''alias'' in the personal {{tt|.bashrc}} file, simply by running the following command:
 +
<bash>echo "alias of211='module load openmpi-i386; source \$HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS'" >> $HOME/.bashrc
 +
</bash>
 +
{{Installation/Linux/AliasNote|OpenFOAM 2.1.1|of211}}
 +
</li>
 +
 +
<li>For x86_64:
 +
<bash>#forcefully load Open-MPI into the environment
 +
module load openmpi-x86_64     
 +
 +
#here you can change 4 to the number of cores you've got
 +
source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI
 +
</bash>
 +
Also, save an ''alias'' in the personal {{tt|.bashrc}} file, simply by running the following command:
 +
<bash>echo "alias of211='module load openmpi-x86_64; source \$HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS'" >> $HOME/.bashrc
 +
</bash>
 +
{{Installation/Linux/AliasNote|OpenFOAM 2.1.1|of211}}
 +
</li>
 +
</ul>
 +
</li>
 +
<li>Now let's build OpenFOAM:<br>
 +
('''Warning''': this may take somewhere from 30 minutes to 6 hours, depending on your machine.)<br>
 +
<bash>#Go into OpenFOAM's main source folder
 +
cd OpenFOAM-2.1.1
 +
 +
# This next command will take a while... somewhere between 30 minutes to 3-6 hours.
 +
./Allwmake > log.make 2>&1
 +
 +
#Run it a second time for getting a summary of the installation
 +
./Allwmake > log.make 2>&1
 +
</bash></li>
 +
 +
<li>{{Installation/Linux/CheckIfAllWentWell}}</li>
  
 
<li>CentOS 6.3 comes with CMake 2.6.4, but ParaView 3.12.0 needs a one of the versions from the more recent CMake 2.8.x series. Therefore, we'll need to do a custom build:
 
<li>CentOS 6.3 comes with CMake 2.6.4, but ParaView 3.12.0 needs a one of the versions from the more recent CMake 2.8.x series. Therefore, we'll need to do a custom build:
 
<bash>cd $WM_THIRD_PARTY_DIR
 
<bash>cd $WM_THIRD_PARTY_DIR
wget "http://www.openfoam.org/mantisbt/file_download.php?file_id=143&type=bug" -O getCmake
+
wget "https://raw.github.com/wyldckat/scripts4OpenFOAM3rdParty/master/getCmake"
 
chmod +x getCmake
 
chmod +x getCmake
 
./getCmake
 
./getCmake
Line 246: Line 373:
 
<li>Now, in order to build ParaView 3.12.0 that comes with OpenFOAM:
 
<li>Now, in order to build ParaView 3.12.0 that comes with OpenFOAM:
 
<bash>cd $WM_THIRD_PARTY_DIR
 
<bash>cd $WM_THIRD_PARTY_DIR
 +
 +
# apply a fix for the more recent OpenGL libraries
 +
sed -i -e 's=//#define GLX_GLXEXT_LEGACY=#define GLX_GLXEXT_LEGACY=' \
 +
  ParaView-3.12.0/VTK/Rendering/vtkXOpenGLRenderWindow.cxx
 +
 
./makeParaView -qmake $(which qmake-qt4)
 
./makeParaView -qmake $(which qmake-qt4)
  
cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers  
+
#quick hack for getting qmake found on the search path
 +
ln -s $(which qmake-qt4) $WM_PROJECT_DIR/bin/qmake
 +
 
 +
cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers
 
wmSET $FOAM_SETTINGS
 
wmSET $FOAM_SETTINGS
 
./Allwclean  
 
./Allwclean  
 
./Allwmake
 
./Allwmake
 
</bash></li>
 
</bash></li>
<li>Now you can go read the User Guide: [http://www.openfoam.org/docs/user/ official OpenFOAM User Guide]</li>
+
<li>{{Installation/ReadUserGuideEtAl_OpenFOAMFoundation}}</li>
 
</ol>
 
</ol>
 +
 +
 +
{{Installation/Linux/AliasReminder|OpenFOAM 2.1.1|of211}}
 +
  
 
'''Discussion thread where you can ask questions about these steps''': [http://www.cfd-online.com/Forums/openfoam-installation/107452-openfoam-installation-sl-6-3-guide-req.html#post383954 OpenFOAM installation in SL 6.3 (guide req)]
 
'''Discussion thread where you can ask questions about these steps''': [http://www.cfd-online.com/Forums/openfoam-installation/107452-openfoam-installation-sl-6-3-guide-req.html#post383954 OpenFOAM installation in SL 6.3 (guide req)]
  
 
[[Category:Installing OpenFOAM on Linux]] [[Category:Installing OpenFOAM on CentOS]]
 
[[Category:Installing OpenFOAM on Linux]] [[Category:Installing OpenFOAM on CentOS]]

Latest revision as of 15:18, 27 October 2018

1 Introduction

This page is dedicated to explaining how to install OpenFOAM OF Version 211.png in:

  • Community ENTerprise Operating System, aka CentOS.
  • Red Hat Enterprise Linux, aka RHEL.
  • Scientific Linux, aka SL.

In theory, all of the above follow the same versioning. Therefore, at the time this page was first written, RHEL, CentOS and SL were all at version 6.3.

Both SL and CentOS derive from RHEL, but CentFOAM is what inspired this page. Therefore, before even trying to follow the instructions on this page, try first CentFOAM.

Last but not least, RHEL uses Fedora as their bleeding edge Linux Distribution, where they test new features. This leads to very close similarities between them, e.g. RHEL 6.3 is very similar to Fedora 14; which means that whatever you can build on Fedora 14, you should also be able to build on RHEL 6.3!

If you do not yet feel comfortable using Linux, then perhaps you better first read the page Working with the Shell and train a bit with the shell/terminal environments, so you can have a better perception of the steps shown below.


2 Copy-Paste steps

A few notes before you start copy-pasting:

  1. Lines that start with # don't have to be copy-pasted. They are just comments to let you know what's going on.
  2. One wrong character is enough for breaking this guide, so make sure you can read the characters properly or that the installed language system does not break the copied characters!


2.1 CentOS 5.1

Note: this was tested with the normal 7 CD-pack of CentOS 5.1 x86_64, installed in a virtual machine.

Discussion thread where you can ask questions about these steps: problem in installation in OpenFOAM-2.1.x on Red Hat

Steps:

  1. Switch to root mode (administrator) and install the necessary packages (run one line at a time):
    su -
    yum groupinstall 'Development Tools' 
    yum install gcc44 gcc44-c++ openmpi openmpi-devel zlib-devel
     
    #these are needed for Qt and ParaView
    yum install libXt-devel libXext-devel libXrender-devel
     
    #This one is useful, but not crucial
    yum upgrade
  2. Continue in step #2 in the section CentOS 5.8.


2.2 CentOS 5.8

Note: this was tested with the normal DVD of CentOS 5.8, installed in a virtual machine.

Discussion thread where you can ask questions about these steps: Installing OpenFOAM 2.1.1 on CentOS 5.x

Steps:

  1. Switch to root mode (administrator), to install the necessary packages:
    sudo -s
    • If the 'sudo' command tells you're not in the sudoers list, then run:
      su -
  2. Install the necessary packages:
    yum groupinstall 'Development Tools' 
    yum install gcc44 gcc44-c++ openmpi openmpi-devel zlib-devel
     
    #This one is useful, but not crucial
    yum upgrade
  3. For building OpenFOAM itself and using the dedicated Open-MPI version, it depends on whether you have installed the i386 or x86_64 architecture of CentOS/SL/RHEL. To check this, run:
    uname -m

    Now, accordingly:

    • For i386:
      #forcefully load Open-MPI into the environment
      mpi-selector --system --set openmpi-1.4-gcc-i386
    • For x86_64:
      #forcefully load Open-MPI into the environment
      mpi-selector --system --set openmpi-1.4-gcc-x86_64
  4. Now exit from the root mode:
    exit
  5. Start a new terminal. This is because you'll need a fully refreshed shell.
  6. Download and unpack (here you can copy-paste all in single go):
    #OpenFOAM downloading and installation
    cd ~
    mkdir OpenFOAM
    cd OpenFOAM
    wget "http://downloads.sourceforge.net/foam/OpenFOAM-2.1.1.tgz?use_mirror=mesh" -O OpenFOAM-2.1.1.tgz
    wget "http://downloads.sourceforge.net/foam/ThirdParty-2.1.1.tgz?use_mirror=mesh" -O ThirdParty-2.1.1.tgz
     
    tar -xzf OpenFOAM-2.1.1.tgz 
    tar -xzf ThirdParty-2.1.1.tgz
  7. According to the previously determined architecture:
    • For i386:
      #here you can change 4 to the number of cores you've got
      source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_COMPILER=Gcc44 WM_MPLIB=SYSTEMOPENMPI WM_ARCH_OPTION=32
      export WM_CC='gcc44'
      export WM_CXX='g++44'
       
      sed -i -e 's=gcc=$(WM_CC)=' OpenFOAM-2.1.1/wmake/rules/linuxGcc44/c
      sed -i -e 's=g++=$(WM_CXX)=' OpenFOAM-2.1.1/wmake/rules/linuxGcc44/c++
    • For x86_64:
      #here you can change 4 to the number of cores you've got
      source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_COMPILER=Gcc44 WM_MPLIB=SYSTEMOPENMPI
      export WM_CC='gcc44'
      export WM_CXX='g++44'
       
      sed -i -e 's=gcc=$(WM_CC)=' OpenFOAM-2.1.1/wmake/rules/linux64Gcc44/c
      sed -i -e 's=g++=$(WM_CXX)=' OpenFOAM-2.1.1/wmake/rules/linux64Gcc44/c++
  8. Save an alias in the personal .bashrc file, simply by running the following commands:
    FULL_SETTINGS="$FOAM_SETTINGS; export WM_CC=gcc44; export WM_CXX=g++44"
    echo "alias of211='source \$HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc ${FULL_SETTINGS}'" >> $HOME/.bashrc
    unset FULL_SETTINGS
    Note: This last line means that whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.1.1 shell environment. In other words, whenever you start a new terminal, you should run:
    of211
    
    For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.
  9. Now let's build OpenFOAM:
    (Warning: this may take somewhere from 30 minutes to 6 hours, depending on your machine.)
    #Go into OpenFOAM's main source folder
    cd OpenFOAM-2.1.1
     
    # This next command will take a while... somewhere between 30 minutes to 3-6 hours.
    ./Allwmake > log.make 2>&1
     
    #Run it a second time for getting a summary of the installation
    ./Allwmake > log.make 2>&1
  10. To check if everything went well:
    1. Check if icoFoam is working, by running this command:
      icoFoam -help

      which should tell you something like this:

      Usage: icoFoam [OPTIONS]
      options:
        -case <dir>       specify alternate case directory, default is the cwd
        -noFunctionObjects
                          do not execute functionObjects
        -parallel         run in parallel
        -roots <(dir1 .. dirN)>
                          slave root directories for distributed running
        -srcDoc           display source code in browser
        -doc              display application documentation in browser
        -help             print the usage

      Note: And keep in mind that you need to be careful with the letter case of the command. It's icoFoam, not icoFOAM.

    2. If the previous command failed to work properly, then edit the file log.make and check if there are any error messages. A few examples on how you can edit this file:
      • By using kwrite:
        kwrite log.make
      • By using gedit:
        gedit log.make
      • By using nano:
        nano log.make

        You can then exit by using the key combination Ctrl+X and following any instructions it gives you.

      Note: It's the first error message that matters.

    3. If you don't understand the output, then please compress the log-file log.make and attach the compressed file to a post in the designated thread.
      If you do not know how to create a compressed file, then try one of the following examples:
      • You can compress the file with gzip by running this command:
        gzip < log.make > log.make.gz

        Then attach the resulting package file named log.make.gz to a post in the designated thread.

      • Or you can compress one or more log-files into a tarball package file, by running this command:
        tar -czf logs.tar.gz log.*

        Then attach the resulting package file named logs.tar.gz to a post in the designated thread.

    4. Instructions on how to further diagnose the issue yourself, have a look at the section Common errors when building OpenFOAM from source code in the page FAQ/Installation and Running.
  11. CentOS 5.8 comes with CMake 2.6.4, but ParaView 3.12.0 needs a one of the versions from the more recent CMake 2.8.x series. Therefore, we'll need to do a custom build:
    cd $WM_THIRD_PARTY_DIR
    wget "https://raw.github.com/wyldckat/scripts4OpenFOAM3rdParty/master/getCmake"
    chmod +x getCmake
    ./getCmake
    ./makeCmake
    wmSET $FOAM_SETTINGS
  12. CentOS 5.8 comes with Qt 4.2.1, but ParaView 3.12.0 needs at least 4.5, with 4.6 as recommended. Therefore, we'll need to do a custom build:
    cd $WM_THIRD_PARTY_DIR
    wget "https://raw.github.com/wyldckat/scripts4OpenFOAM3rdParty/master/getQt"
    chmod +x getQt
    ./getQt
     
    #fix the defaults for Qt not to use gcc or g++ by default
    sed -i -e 's/= gcc/= gcc44/' qt-everywhere-opensource-src-4.6.4/mkspecs/common/g++.conf
    sed -i -e 's/= g++/= g++44/' qt-everywhere-opensource-src-4.6.4/mkspecs/common/g++.conf
     
    ./makeQt 4.6.4 > log.mkqt 2>&1
  13. Now, in order to build ParaView 3.12.0 that comes with OpenFOAM, along with the Qt version recently built:
    cd $WM_THIRD_PARTY_DIR
    ./makeParaView -qmake $WM_THIRD_PARTY_DIR/platforms/$WM_ARCH$WM_COMPILER/qt-4.6.4/bin/qmake PARAVIEW_INSTALL_THIRD_PARTY_LIBRARIES:BOOL=ON
     
    cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers 
    wmSET $FOAM_SETTINGS
    export PATH=$WM_THIRD_PARTY_DIR/platforms/$WM_ARCH$WM_COMPILER/qt-4.6.4/bin:$PATH
    ./Allwclean 
    ./Allwmake
  14. Now you can go read the User Guide, where you may have more than one choice:
    1. Which you can find a local copy of the User Guide by running the following command:
      ls -A1 $WM_PROJECT_DIR/doc/Guides*/*UserGuide*.pdf
      • You should see two available formats: A4 and US-Letter.
      • But if it instead tells you that there is No such file or directory, then the OpenFOAM environment is possibly not properly activated.
    2. You can also find the more recent OpenFOAM Foundation User Guides online at the following page: official OpenFOAM User Guide - but be careful if you use the version that is too much ahead of the version you are currently using, given that some features have changed overtime.


Reminder: Whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.1.1 shell environment. In other words, run the following command whenever you start a new terminal:
of211
For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.


Discussion thread where you can ask questions about these steps: Installing OpenFOAM 2.1.1 on CentOS 5.x


2.3 CentOS 6.3

Note: this was tested with the LiveDVD's of CentOS 6.3, installed in a virtual machine.

Discussion thread where you can ask questions about these steps: OpenFOAM installation in SL 6.3 (guide req)

Steps:

  1. Switch to root mode (administrator), to install the necessary packages:
    sudo -s
    • If the 'sudo' command tells you're not in the sudoers list, then run:
      su -
  2. Install the necessary packages:
    yum groupinstall 'Development Tools' 
    yum install openmpi openmpi-devel qt-devel qt-webkit-devel zlib-devel
     
    #This one is useful, but not crucial
    yum upgrade
  3. Now exit from the root mode:
    exit
  4. Start a new terminal. This is because you'll need a fully refreshed shell.
  5. Download and unpack (here you can copy-paste all in single go):
    #OpenFOAM downloading and installation
    cd ~
    mkdir OpenFOAM
    cd OpenFOAM
    wget "http://downloads.sourceforge.net/foam/OpenFOAM-2.1.1.tgz?use_mirror=mesh" -O OpenFOAM-2.1.1.tgz
    wget "http://downloads.sourceforge.net/foam/ThirdParty-2.1.1.tgz?use_mirror=mesh" -O ThirdParty-2.1.1.tgz
     
    tar -xzf OpenFOAM-2.1.1.tgz 
    tar -xzf ThirdParty-2.1.1.tgz
  6. For building OpenFOAM itself, it depends on whether you have installed the i386 or x86_64 architecture of CentOS/SL/RHEL. To check this, run:
    uname -m

    Now, accordingly:

    • For i386:
      #forcefully load Open-MPI into the environment
      module load openmpi-i386
       
      #here you can change 4 to the number of cores you've got
      source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI WM_ARCH_OPTION=32

      Also, save an alias in the personal .bashrc file, simply by running the following command:

      echo "alias of211='module load openmpi-i386; source \$HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS'" >> $HOME/.bashrc
      Note: This last line means that whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.1.1 shell environment. In other words, whenever you start a new terminal, you should run:
      of211
      
      For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.
    • For x86_64:
      #forcefully load Open-MPI into the environment
      module load openmpi-x86_64       
       
      #here you can change 4 to the number of cores you've got
      source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI

      Also, save an alias in the personal .bashrc file, simply by running the following command:

      echo "alias of211='module load openmpi-x86_64; source \$HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS'" >> $HOME/.bashrc
      Note: This last line means that whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.1.1 shell environment. In other words, whenever you start a new terminal, you should run:
      of211
      
      For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.
  7. Now let's build OpenFOAM:
    (Warning: this may take somewhere from 30 minutes to 6 hours, depending on your machine.)
    #Go into OpenFOAM's main source folder
    cd OpenFOAM-2.1.1
     
    # This next command will take a while... somewhere between 30 minutes to 3-6 hours.
    ./Allwmake > log.make 2>&1
     
    #Run it a second time for getting a summary of the installation
    ./Allwmake > log.make 2>&1
  8. To check if everything went well:
    1. Check if icoFoam is working, by running this command:
      icoFoam -help

      which should tell you something like this:

      Usage: icoFoam [OPTIONS]
      options:
        -case <dir>       specify alternate case directory, default is the cwd
        -noFunctionObjects
                          do not execute functionObjects
        -parallel         run in parallel
        -roots <(dir1 .. dirN)>
                          slave root directories for distributed running
        -srcDoc           display source code in browser
        -doc              display application documentation in browser
        -help             print the usage

      Note: And keep in mind that you need to be careful with the letter case of the command. It's icoFoam, not icoFOAM.

    2. If the previous command failed to work properly, then edit the file log.make and check if there are any error messages. A few examples on how you can edit this file:
      • By using kwrite:
        kwrite log.make
      • By using gedit:
        gedit log.make
      • By using nano:
        nano log.make

        You can then exit by using the key combination Ctrl+X and following any instructions it gives you.

      Note: It's the first error message that matters.

    3. If you don't understand the output, then please compress the log-file log.make and attach the compressed file to a post in the designated thread.
      If you do not know how to create a compressed file, then try one of the following examples:
      • You can compress the file with gzip by running this command:
        gzip < log.make > log.make.gz

        Then attach the resulting package file named log.make.gz to a post in the designated thread.

      • Or you can compress one or more log-files into a tarball package file, by running this command:
        tar -czf logs.tar.gz log.*

        Then attach the resulting package file named logs.tar.gz to a post in the designated thread.

    4. Instructions on how to further diagnose the issue yourself, have a look at the section Common errors when building OpenFOAM from source code in the page FAQ/Installation and Running.
  9. CentOS 6.3 comes with CMake 2.6.4, but ParaView 3.12.0 needs a one of the versions from the more recent CMake 2.8.x series. Therefore, we'll need to do a custom build:
    cd $WM_THIRD_PARTY_DIR
    wget "https://raw.github.com/wyldckat/scripts4OpenFOAM3rdParty/master/getCmake"
    chmod +x getCmake
    ./getCmake
    ./makeCmake
    wmSET $FOAM_SETTINGS
  10. Now, in order to build ParaView 3.12.0 that comes with OpenFOAM:
    cd $WM_THIRD_PARTY_DIR
    ./makeParaView -qmake $(which qmake-qt4)
     
    #quick hack for getting qmake found on the search path
    ln -s $(which qmake-qt4) $WM_PROJECT_DIR/bin/qmake
     
    cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers 
    wmSET $FOAM_SETTINGS
    ./Allwclean 
    ./Allwmake
  11. Now you can go read the User Guide, where you may have more than one choice:
    1. Which you can find a local copy of the User Guide by running the following command:
      ls -A1 $WM_PROJECT_DIR/doc/Guides*/*UserGuide*.pdf
      • You should see two available formats: A4 and US-Letter.
      • But if it instead tells you that there is No such file or directory, then the OpenFOAM environment is possibly not properly activated.
    2. You can also find the more recent OpenFOAM Foundation User Guides online at the following page: official OpenFOAM User Guide - but be careful if you use the version that is too much ahead of the version you are currently using, given that some features have changed overtime.


Reminder: Whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.1.1 shell environment. In other words, run the following command whenever you start a new terminal:
of211
For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.


Discussion thread where you can ask questions about these steps: OpenFOAM installation in SL 6.3 (guide req)


2.4 CentOS 6.7

Discussion thread where you can ask questions about these steps: OpenFOAM installation in SL 6.3 (guide req)

Steps:

  1. Switch to root mode (administrator), to install the necessary packages:
    sudo -s
    • If the 'sudo' command tells you're not in the sudoers list, then run:
      su -
  2. Install the necessary packages:
    yum groupinstall 'Development Tools' 
    yum install openmpi openmpi-devel qt-devel qt-webkit-devel zlib-devel
     
    #This one is useful, but not crucial
    yum upgrade
  3. Now exit from the root mode:
    exit
  4. Start a new terminal. This is because you'll need a fully refreshed shell.
  5. Download and unpack (here you can copy-paste all in single go):
    #OpenFOAM downloading and installation
    cd ~
    mkdir OpenFOAM
    cd OpenFOAM
    wget "http://downloads.sourceforge.net/foam/OpenFOAM-2.1.1.tgz?use_mirror=mesh" -O OpenFOAM-2.1.1.tgz
    wget "http://downloads.sourceforge.net/foam/ThirdParty-2.1.1.tgz?use_mirror=mesh" -O ThirdParty-2.1.1.tgz
     
    tar -xzf OpenFOAM-2.1.1.tgz 
    tar -xzf ThirdParty-2.1.1.tgz
  6. For building OpenFOAM itself, it depends on whether you have installed the i386 or x86_64 architecture of CentOS/SL/RHEL. To check this, run:
    uname -m

    Now, accordingly:

    • For i386:
      #forcefully load Open-MPI into the environment
      module load openmpi-i386
       
      #here you can change 4 to the number of cores you've got
      source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI WM_ARCH_OPTION=32

      Also, save an alias in the personal .bashrc file, simply by running the following command:

      echo "alias of211='module load openmpi-i386; source \$HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS'" >> $HOME/.bashrc
      Note: This last line means that whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.1.1 shell environment. In other words, whenever you start a new terminal, you should run:
      of211
      
      For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.
    • For x86_64:
      #forcefully load Open-MPI into the environment
      module load openmpi-x86_64       
       
      #here you can change 4 to the number of cores you've got
      source $HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI

      Also, save an alias in the personal .bashrc file, simply by running the following command:

      echo "alias of211='module load openmpi-x86_64; source \$HOME/OpenFOAM/OpenFOAM-2.1.1/etc/bashrc $FOAM_SETTINGS'" >> $HOME/.bashrc
      Note: This last line means that whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.1.1 shell environment. In other words, whenever you start a new terminal, you should run:
      of211
      
      For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.
  7. Now let's build OpenFOAM:
    (Warning: this may take somewhere from 30 minutes to 6 hours, depending on your machine.)
    #Go into OpenFOAM's main source folder
    cd OpenFOAM-2.1.1
     
    # This next command will take a while... somewhere between 30 minutes to 3-6 hours.
    ./Allwmake > log.make 2>&1
     
    #Run it a second time for getting a summary of the installation
    ./Allwmake > log.make 2>&1
  8. To check if everything went well:
    1. Check if icoFoam is working, by running this command:
      icoFoam -help

      which should tell you something like this:

      Usage: icoFoam [OPTIONS]
      options:
        -case <dir>       specify alternate case directory, default is the cwd
        -noFunctionObjects
                          do not execute functionObjects
        -parallel         run in parallel
        -roots <(dir1 .. dirN)>
                          slave root directories for distributed running
        -srcDoc           display source code in browser
        -doc              display application documentation in browser
        -help             print the usage

      Note: And keep in mind that you need to be careful with the letter case of the command. It's icoFoam, not icoFOAM.

    2. If the previous command failed to work properly, then edit the file log.make and check if there are any error messages. A few examples on how you can edit this file:
      • By using kwrite:
        kwrite log.make
      • By using gedit:
        gedit log.make
      • By using nano:
        nano log.make

        You can then exit by using the key combination Ctrl+X and following any instructions it gives you.

      Note: It's the first error message that matters.

    3. If you don't understand the output, then please compress the log-file log.make and attach the compressed file to a post in the designated thread.
      If you do not know how to create a compressed file, then try one of the following examples:
      • You can compress the file with gzip by running this command:
        gzip < log.make > log.make.gz

        Then attach the resulting package file named log.make.gz to a post in the designated thread.

      • Or you can compress one or more log-files into a tarball package file, by running this command:
        tar -czf logs.tar.gz log.*

        Then attach the resulting package file named logs.tar.gz to a post in the designated thread.

    4. Instructions on how to further diagnose the issue yourself, have a look at the section Common errors when building OpenFOAM from source code in the page FAQ/Installation and Running.
  9. CentOS 6.3 comes with CMake 2.6.4, but ParaView 3.12.0 needs a one of the versions from the more recent CMake 2.8.x series. Therefore, we'll need to do a custom build:
    cd $WM_THIRD_PARTY_DIR
    wget "https://raw.github.com/wyldckat/scripts4OpenFOAM3rdParty/master/getCmake"
    chmod +x getCmake
    ./getCmake
    ./makeCmake
    wmSET $FOAM_SETTINGS
  10. Now, in order to build ParaView 3.12.0 that comes with OpenFOAM:
    cd $WM_THIRD_PARTY_DIR
     
    # apply a fix for the more recent OpenGL libraries
    sed -i -e 's=//#define GLX_GLXEXT_LEGACY=#define GLX_GLXEXT_LEGACY=' \
      ParaView-3.12.0/VTK/Rendering/vtkXOpenGLRenderWindow.cxx
     
    ./makeParaView -qmake $(which qmake-qt4)
     
    #quick hack for getting qmake found on the search path
    ln -s $(which qmake-qt4) $WM_PROJECT_DIR/bin/qmake
     
    cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers
    wmSET $FOAM_SETTINGS
    ./Allwclean 
    ./Allwmake
  11. Now you can go read the User Guide, where you may have more than one choice:
    1. Which you can find a local copy of the User Guide by running the following command:
      ls -A1 $WM_PROJECT_DIR/doc/Guides*/*UserGuide*.pdf
      • You should see two available formats: A4 and US-Letter.
      • But if it instead tells you that there is No such file or directory, then the OpenFOAM environment is possibly not properly activated.
    2. You can also find the more recent OpenFOAM Foundation User Guides online at the following page: official OpenFOAM User Guide - but be careful if you use the version that is too much ahead of the version you are currently using, given that some features have changed overtime.


Reminder: Whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.1.1 shell environment. In other words, run the following command whenever you start a new terminal:
of211
For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.


Discussion thread where you can ask questions about these steps: OpenFOAM installation in SL 6.3 (guide req)