[pgiannuzzi]

I am trying to install 2.3.0 on CentOS 5.10 using the installation tutorial at:
http://openfoamwiki.net/index.php/In...CentOS_SL_RHEL

When I get to the openFOAM build check (step 16) icoFoam does not exist. I also find the following error in the make.log:
error: call of overloaded

I have attached part of the make.log, the entire make.log is too large to attach. Any insight you can provide would be greatly appreciated.

[wyldckat]

Greetings pgiannuzzi and welcome to the forum!

Sorry for taking so long to answer back, but I didn't manage to have enough time to come to the forum any sooner.

I don't know if you've managed to solve this issue or not, but from what I can see from the log file you're attached, there are two issues that seem to have occurred:

1. You're building as "root", namely with administrative powers. This is dangerous as one wrong step is more than enough to damage your system installation and have to reinstall everything again if something critical is damaged. My guess is that you missed the step #4 which explicitly states that you should run the command "exit" before proceeding, as this will exit from root mode .
2. The first error message I could see in the log file leads me to believe that the correct GCC 4.8 compiler was not built with success. If you go into the ThirdParty-2.3.0 folder:
   

   cd $WM_THIRD_PARTY_DIR

   there are 2 files there: "mkgcc.log" and "mkbinutils.log" - which should tell us what happened when GCC and binutils were built with success or not.
   The simplest test is to simply run:
   

   gcc --version

   If it does not state something about being the version 4.8.1, then something definitely went wrong and those 2 files should tell us why.

Best regards,
Bruno

[pgiannuzzi]

Bruno -

Thank you very much for your help. I see what you are saying about installing as root. I deleted the OpenFOAM directory that I had created as root and went through the steps again as a new user (including exiting at step 4).
Now when I type: gcc --version
I get: gcc (OpenFOAM) 4.8.1
This makes me think that gcc was installed ok and I do not need to go through the large mkgcc.log and mkbinutils.log files in detail (correct me if I am wrong).

I run into problems after step 15. Looking in the make.log I see:

cp -f ../bin/d[agm]* /home/pgiannuzzi/OpenFOAM/ThirdParty-2.3.0/platforms/linux64Gcc48/scotch_6.0.0/bin
cp: cannot stat `../bin/d[agm]*': No such file or directory
make: [install] Error 1 (ignored)

This is causing be to run into problems when I get to step 18 and try to make paraview I get:

qmake not found under specified QMAKE_PATH
      QMAKE_PATH=/home/pgiannuzzi/OpenFOAM/ThirdPARTY-2.3.0/platforms/linux64Gcc48/qt-4.8.4/bin/qmake
leaving unspecified
  
 *** Error: cannot find qmake either at $QMAKE_PATH or in current $PATH

This is because there is no qt-4.8.4 directory within the linux64Gcc48 directory.

Any thoughts on this one. If I havn't given you enough info, please let me know what I can provide that might help.

Thanks again;
Paul

[wyldckat]

Hi Paul,

Originally Posted by pgiannuzzi

I run into problems after step 15. Looking in the make.log I see:

cp -f ../bin/d[agm]* /home/pgiannuzzi/OpenFOAM/ThirdParty-2.3.0/platforms/linux64Gcc48/scotch_6.0.0/bin
cp: cannot stat `../bin/d[agm]*': No such file or directory
make: [install] Error 1 (ignored)

Actually, that's a false positive, i.e. that error message can be ignored, as the parenthesis imply. It occurs when the Allwmake script in the "ThirdParty-*" folder is cleaning up after the Scotch library has been built. This is because the source code folder is that same one used for building as well, which can lead to conflicts if you want to build more than one architecture (e.g. to have both 32 and 64-bit).
If there are any other errors in the "make.log" file following that one, than those are most likely the ones to be concerned about.

Originally Posted by pgiannuzzi

This is causing be to run into problems when I get to step 18 and try to make paraview I get:

qmake not found under specified QMAKE_PATH
      QMAKE_PATH=/home/pgiannuzzi/OpenFOAM/ThirdPARTY-2.3.0/platforms/linux64Gcc48/qt-4.8.4/bin/qmake
leaving unspecified
  
 *** Error: cannot find qmake either at $QMAKE_PATH or in current $PATH

This is because there is no qt-4.8.4 directory within the linux64Gcc48 directory.

OK, in this case we need to look at the file "mkqt.log", which should tell us what went wrong, or at the very least, hint at what went wrong when trying to build Qt.

Best regards,
Bruno

[pgiannuzzi]

Thanks Bruno;

I skimmed through the mkqt.log and found this text at the end of the log:

qcryptographichash.o qxmlstream.o qxmlutils.o-m64
Basic XLib functionality test failed!
You might need to modify the include and library search paths by editing
QMAKE_INCDIR_X11 and QMAKE_LIBDIR_X11 in /home/pgiannuzzi/OpenFOAM/ThirdParty-2.3.0/qt-everywhere-opensource-src-4.8.4/mkspecs/linux-g64.
Error building: Qt-4.8.4

I went looking for the Linux-g64 folder in mkspecs and it is not there. Any clues on how to tackle this one? Is there a preferred method of installing Xlib?

Paul

[wyldckat]

Hi Paul,

Sorry about that . I don't know what happened when I wrote the instructions, but somewhere along the line I forgot to write down all of the packages that are needed for CentOS 5.10.

I've updated the wiki page a few minutes ago: http://openfoamwiki.net/index.php/In...EL#CentOS_5.10
But just in case, here is the complete installation command for the necessary packages:

yum install openmpi openmpi-devel zlib-devel readline-devel ncurses-devel \
texinfo gstreamer-plugins-base-devel libXext-devel libGLU-devel libXt-devel \
libXrender-devel libXinerama-devel libpng-devel libXrandr-devel libXi-devel \
libXft-devel libXcursor-devel

Then you can skip to step #17, run the first and last line on that step. This is because most of the missing packages are related to building Qt and ParaView.

Hopefully this fixes all of the remaining problems.

Best regards,
Bruno

[vmgbritt]

Hi,


Thank you for developing such detailed instructions for installation of OpenFOAM on RHEL systems. I might be a bit overzealous but I jumped straight into installing 2.3.1 rather than 2.3.0 ...

I've followed your directions installing OF 2.3.1 onto A Centos 5.11 X86_64 machine.

I'm getting compilation issues and it appears the problem lies in the gcc compiler not being recognized. The mkgcc.log indicates gcc-4.8.1 is installed and built but if I execute gcc --version I get nothing. If I execute gcc -v I get 4.1.2 which was initially installed. I tried adapting your
sed -i -e 's=gcc\-4\.8\.2=gcc-4.8.1=' OpenFOAM-2.3.0/etc/config/settings.sh

to
sed -i -e 's=gcc\-4\.1\.2=gcc-4.8.1=' OpenFOAM-2.3.0/etc/config/settings.sh

Again no success.

I tried installing from devtoolset1.1 but again still gcc --version returns 4.1.2.

Pretty sure that my issues relate to the compiler version not being recognized.

Attached a zip file with log files if it would help.

Appreciate any insight you can provide.

All the best for the Holiday Season to everyone.

Britt

[wyldckat]

Greetings Britt and welcome to posting on the forum!

Originally Posted by vmgbritt

I might be a bit overzealous but I jumped straight into installing 2.3.1 rather than 2.3.0 ...

Uhm... "overzealous" is not the word I would use... perhaps "courageous", but not "overzealous"

About 3-4 days after you posted your question, I managed to copy-paste-adapt the installation instructions for OpenFOAM 2.3.1, which you can now find here: http://openfoamwiki.net/index.php/In...EL#CentOS_5.10

My advice: delete the folders "OpenFOAM-2.3.1" and "ThirdParty-2.3.1" from within the folder "~/OpenFOAM". Then you might not need to run wget in step #6, but otherwise double-check if all other steps are done exactly as they are written

Best regards,
Bruno

[vmgbritt]

Bruno,

Thanks for updating with the 2.3.1 instructions. I thought it was identical to what I had done previously but I guess not. At any rate it is running successfully now.

Further question that may or may not fit here. No that I have it built on one machine what is the "best" method of packaging this install to roll out to the additional 13 cluster machines I have [all identical architecture?]. I'd rather not build it on each machine ? !

Thanks,

Britt

[wyldckat]

Hi Britt,

I'm glad it's working!

As for the deployment in multiple machines, it might depend on the level of detail you want on the slave nodes. The critical folders (if my memory serves me right) that can simply be copied are:

• OpenFOAM-2.3.1
  • bin
  • etc
  • platforms
• ThirdParty-2.3.1
  • platforms

Beyond that, it's only needed for the main machine or workstation for developing any new changes.

Best regards,
Bruno

[cfdopenfoam]

unfortunately i faced the same problem with paraview-4.1.0 installation.

i followed the guidelines http://www.openfoam.org/archive/2.3....oad/source.php
but i got this :

Built: cmake-2.8.12.1
yk@yk-VirtualBox:~/OpenFOAM/ThirdParty-2.3.0$ cd $WM_THIRD_PARTY_DIR
yk@yk-VirtualBox:~/OpenFOAM/ThirdParty-2.3.0$ ./makeParaView4 

ParaView_SOURCE_DIR=/home/yk/OpenFOAM/ThirdParty-2.3.0/ParaView-4.1.0
ParaView_BINARY_DIR=/home/yk/OpenFOAM/ThirdParty-2.3.0/build/linux64Gcc/ParaView-4.1.0
ParaView_DIR=/home/yk/OpenFOAM/ThirdParty-2.3.0/platforms/linux64Gcc/ParaView-4.1.0
sed: can't read /home/yk/OpenFOAM/ThirdParty-2.3.0/ParaView-4.1.0/VTK/Utilities/kwsys/kwsysDateStamp.cmake: No such file or directory
date-stamp: 

Build stages selected
---------------------
    -config   true
    -make     true
    -install  true
---------------------
Features selected
    mesa      false
    mpi       false
    python    false
    qt        true
---------------------
Version information
    qt        4.8.1
    version   4.1.0
    major     4.1
    build     Release
MISMATCH!
    specified 4.1.0
    found     
---------------------
----
Configuring paraview-4.1.0 (major version: 4.1)
    MPI    support : false
    Python support : false
    MESA   support : false
    Qt dev support : true
    Source         : /home/yk/OpenFOAM/ThirdParty-2.3.0/ParaView-4.1.0
    Build          : /home/yk/OpenFOAM/ThirdParty-2.3.0/build/linux64Gcc/ParaView-4.1.0
    Target         : /home/yk/OpenFOAM/ThirdParty-2.3.0/platforms/linux64Gcc/ParaView-4.1.0
    Build type     : Release
----

cmake -DCMAKE_INSTALL_PREFIX:PATH=/home/yk/OpenFOAM/ThirdParty-2.3.0/platforms/linux64Gcc/ParaView-4.1.0 -DBUILD_SHARED_LIBS:BOOL=ON VTK_USE_RPATH:BOOL=OFF -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON -DBUILD_TESTING:BOOL=OFF -DPARAVIEW_BUILD_QT_GUI=ON -DCMAKE_BUILD_TYPE:STRING=Release /home/yk/OpenFOAM/ThirdParty-2.3.0/ParaView-4.1.0

----

CMake Error at CMakeLists.txt:31 (cmake_minimum_required):
  CMake 2.8.8 or higher is required.  You are running version 2.8.7


-- Configuring incomplete, errors occurred!
    Starting make
make: *** No targets specified and no makefile found.  Stop.
Command exited with non-zero status 2
0.00user 0.00system 0:00.00elapsed 0%CPU (0avgtext+0avgdata 4480maxresident)k
0inputs+0outputs (0major+331minor)pagefaults 0swaps
    Done make
    Installing ParaView to /home/yk/OpenFOAM/ThirdParty-2.3.0/platforms/linux64Gcc/ParaView-4.1.0
make: *** No rule to make target `install'.  Stop.
    ---
    Installation complete for paraview-4.1.0
    Set environment variables:

        export ParaView_DIR=/home/yk/OpenFOAM/ThirdParty-2.3.0/platforms/linux64Gcc/ParaView-4.1.0
        export PATH=$ParaView_DIR/bin:$PATH
        export PV_PLUGIN_PATH=$FOAM_LIBBIN/paraview-4.1
    ---

Done

any help? thsnks a lot.

Originally Posted by wyldckat

Greetings Mike and welcome to the forum!

My first suspicion is that the error message you're getting is related to the build being made as superuser, i.e. as root. The installation instructions on the wiki were designed for building as normal user, not as root, because that way it's less likely that the person following the wiki page to skip an important step and mistakenly make an error, and when trying to fix it, accidentally completely destroys the whole system installation...

My second suspicion is that you ran out of disk space on the partition that has the folder "/opt".

My third suspicion is that "/opt" is an NFS mount, which can lead to seriously major problems when doing trying to build source code over a shared network folder, because it's a lot easier this way for metadata to not be up-to-date on time of the build.

If possible, please retry following the build instructions as a normal user. Once the build is completely done, you can copy or move only the important folders+files of the installation to "/opt" and then use chown and chmod for restoring the correct permissions.

Best regards,
Bruno

[wyldckat]

Originally Posted by cfdopenfoam

Built: cmake-2.8.12.1
yk@yk-VirtualBox:~/OpenFOAM/ThirdParty-2.3.0$ cd $WM_THIRD_PARTY_DIR
yk@yk-VirtualBox:~/OpenFOAM/ThirdParty-2.3.0$ ./makeParaView4 
[...]

CMake Error at CMakeLists.txt:31 (cmake_minimum_required):
  CMake 2.8.8 or higher is required.  You are running version 2.8.7

Quick answer: If you had followed one of the following instructions:

• http://www.openfoam.org/download/source.php
• http://openfoamwiki.net/index.php/In...EL#CentOS_5.10 - specifically in step #10

you would have seen what's missing, namely the need to execute this command:

wmSET

after building CMake.

[cfdopenfoam]

thank you very much for timely reply. hope that someone could see this when installing OF-2.3.0 because the command wmSET is missing in the corresponding guidelines while included in the new version of 2.3.1.

PS: i am almost new to OF and linux but i've learned a lot and solverd my own problems with the help of this forum. thanks for all!

Originally Posted by wyldckat

Quick answer: If you had followed one of the following instructions:

• http://www.openfoam.org/download/source.php
• http://openfoamwiki.net/index.php/In...EL#CentOS_5.10 - specifically in step #10

you would have seen what's missing, namely the need to execute this command:

wmSET

after building CMake.