[mhkenergy]

Hi all,

I am using Scientific Linux and I tried to install foam extend 3.0 WITHOUT installing the original OpenFoam 2.x.x. I followed the instructions on the openfoam wiki website given for Fedora (which is the one that should be followed for the package system SL is using). foam extend's own packages seem to have installed fine, but I am having problems with ThirdParty. For your information, I am trying to use the qt47-devel package which should be fine to compile ParaView 4.0.1, and I am showing the correct path to the bin directory of qt that comes with it. My prefs.sh has this line to point to QT_DIR_BIN:

 export QT_BIN_DIR=/usr/lib64/qt47/bin/

However, when I try

 $ ./ThirdParty/AllMake.pre >& ThirdParty/log_AllMake.pre

in shell and later check the log file the output of the thirdparty installation process is directed to, I see the following error:

 RPM build errors:
    Bad exit status from /home/silverwolf/foam/foam-extend-3.0/ThirdParty/rpmBuild/tmp/rpm-tmp.qZ98vr (%build)
Installing package: ParaView-4.0.1
  Uninstalling ParaView-4.0.1 using RPM: ParaView-4.0.1-linux64GccDPOpt.x86_64
  Installing ParaView-4.0.1 using RPM file:  /home/silverwolf/foam/foam-extend-3.0/ThirdParty/rpmBuild/RPMS/x86_64/ParaView-4.0.1-linux64GccDPOpt.x86_64.rpm
error: open of  /home/silverwolf/foam/foam-extend-3.0/ThirdParty/rpmBuild/RPMS/x86_64/ParaView-4.0.1-linux64GccDPOpt.x86_64.rpm  failed: No such file or directory

I would be glad for your help.

[wyldckat]

Greetings mhkenergy and welcome to the forum!

Scientific Linux is very similar to CentOS and RHEL. You didn't mention which version you're using, so I'll have to guess that you might be using SL 6.5, therefore please try following the instructions given here: http://www.cfd-online.com/Forums/ope...tml#post483525 post #4

Best regards,
Bruno

[mhkenergy]

wyldkat, thank you for your reply. Yes, I am using Scientific Linux release 6.5. I will look at the post you recommended and post back whether it works or not.

[mhkenergy]

Unfortunately, still no progress. With gcc v4.8.2 and qt-devel v4.7 I am using for the installation process, I am still getting the same error:

RPM build errors:
    Bad exit status from /home/silverwolf/foam/foam-extend-3.0/ThirdParty/rpmBuild/tmp/rpm-tmp.jcIpE6 (%build)
Installing package: ParaView-4.0.1
  Uninstalling ParaView-4.0.1 using RPM: ParaView-4.0.1-linux64GccDPOpt.x86_64
  Installing ParaView-4.0.1 using RPM file: /home/silverwolf/foam/foam-extend-3.0/ThirdParty/rpmBuild/RPMS/x86_64/ParaView-4.0.1-linux64GccDPOpt.x86_64.rpm
error: open of /home/silverwolf/foam/foam-extend-3.0/ThirdParty/rpmBuild/RPMS/x86_64/ParaView-4.0.1-linux64GccDPOpt.x86_64.rpm failed: No such file or directory

I've just checked Hakan Nilsson's webpage on openfoam extend 3.0 installation (which seems like the most detailed one existing on the web with some nice tricks, and details included), but at the end of the page he also reports this:

Note also that we are here using the OpenFOAM reader distributed with Paraview, which is slightly different from the one distributed with OpenFOAM. I was not able to make the one distributed with foam-extend-3.0 work.

Can this be because I am trying to install foam extend 3.0 without installing the original OpenFoam 2.x.x beforehand that sets up its own ParaView?

I would be glad if someone can help me with this without making me install ParaView separately from binary.

[hani]

Hi,

The quote is for Ubuntu. That is about the OpenFOAM reader for paraFoam, which is not the same as compiling ParaView. We still have that problem with the reader for Ubuntu.

I also had problems installing ParaView in REDHAT, but just recently I figured out a way to make it work in our system.

Before compiling ParaView, do:
export WM_NCOMPPROCS=1

Let me know if that is helpful for you as well.

Best regards,
Håkan

[mhkenergy]

Hi Hakan,

Thank you for your reply. However, I still get the same error after trying your advice and putting it to $WM_PROJECT_DIR/etc/prefs.sh. ParaView had first warned when I was doing my first Install with a lesser version of qt, but then I installed qt 4.7 which was stated in that first Install error message to be sufficient for compiling ParaView 4.0.1. Would running AllClean script before attempting this be useful?

I am attaching my logfile in case someone would like to to check and think about the problem encountered. There are a few other things like scotch and parmetis, but currently I am just concentrated on the ParaView compile problem. You can see the paraView error part close to the end of the log-file in attachment.

[hani]

The error message is the same for all the packages that fail, so it is not specific to ParaView:

Error: expecting string instruction after `rep'

Googling for this, I see that some people had problems with gcc versions and binutils.

I use

as --version
--------------
GNU assembler version 2.20.51.0.2-5.36.el6 20100205

gcc --version
---------------
gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)

If you would like to try, you can uncomment different lines for gcc/gmp/mpfr/mpc in AllMake.stage.1 to compile other versions of gcc. Of course, you may have to change your foam-extend environment so that the new version is used. It may help.

Google a bit for this error message and see what you find.

Håkan

[mhkenergy]

So far my experience with installing foam extend 3.0 on Scientific Linux 6.5:
I tried 4 different combinations of installations that would result from pairing gcc versions 4.8.2 & 4.4.7 with Qt v4.7 & QT_THIRD_PARTY (which if I don't remember wrong is Qt v4.8.5). I also have binutils-devel v2.20.51 that is provided by sl6x repo. It appears that the compilation process of ParaView 4.0.1 that comes with foam extend 3.0 does not like gcc v4.8.2; which resulted not only in errors in ParaView compilation but also in scotch and parametis. On the ParaView side, it gave "Error: expecting string instruction after `rep'". Then I disabled gcc v4.8.2 and switched to 4.4.7 which handled the installation of scotch and parametis, and compiled ParaView a long way up to 88% until it quit by providing the error below for both system installed Qt v4.7 and QT_THIRD_PARTY=1 options:

[ 88%] Generating ui_pqBarChartOptionsWidget.h
Generating ui_pqApplicationOptions.h
uic: Error in line 115, column 61 : Unexpected attribute alignment
File '/home/silverwolf/foam/foam-extend-3.0/ThirdParty/rpmBuild/BUILD/ParaView-v4.0.1-source/Qt/Components/Resources/UI/pqApplicationOptions.ui' is not valid
make[2]: *** [Qt/Components/ui_pqApplicationOptions.h] Error 1
make[2]: *** Waiting for unfinished jobs....
[ 88%] Generating ui_pqBoxWidget.h
make[1]: *** [Qt/Components/CMakeFiles/pqComponents.dir/all] Error 2
make: *** [all] Error 2
error: Bad exit status from /home/silverwolf/foam/foam-extend-3.0/ThirdParty/rpmBuild/tmp/rpm-tmp.ErU441 (%build)

On the other hand, thanks to Hakan Nilsson for his interest and advice, I tried setting WM_NCOMPPROCS=1 for the installations I carried out using gcc v4.8.2 but unfortunately they did not work. One more attempt with this setting paired up with gcc v4.4.7 can be tried, which I haven't yet.

I will look into what this error I posted above might mean, but as of now I am not very hopeful in terms of how this is going to get solved since I've already spent way too much time on trying to make this work among a million things I have to deal with my research. Please feel free to have look at my attached prefs.sh and ThirdParty installation process logfile if you're interested.

Thanks again everyone for sharing their opinions and knowledge about the problem. I would be glad for further assistance.

Best regards,

[mhkenergy]

Folks, at last I have good news

I was able to compile ParaView 4.0.1 after long tries but the solution came after a surprising update from Qt itself. Today when I tried to run $WM_THIRD_PARTY_DIR/AllMake.stage4 , I saw that the connection to the package url failed. I looked on the web to see if the Qt download links were dead, and indeed I saw that on June 2 they updated 4.8 series version to 4.8.6 from 4.8.5 which was the version that came with foam extend 3.0 itself. And since I couldn't compile ParaView on SL 6.5 with both Qt v4.7 (System installed Qt version) and Qt 4.8.5 (QT_THIRD_PARTY=1 version), I manipulated a few files so that I could connect to the recently updated Qt package download server and install Qt 4.8.6 with proper environment variables. These were namely:

• $WM_THIRD_PARTY_DIR/AllMake.stage4 (for the correct download link required for v4.8.6)

• $WM_PROJECT_DIR/settings.sh

What needs to be done with these files is that you need to replace every Qt related occurrence of "4.8.5" with "4.8.6". Later if I have time, I could write simple one line shell commands that can carry out these for anyone automatically, but I think even the most novice user can manipulate these files with vi, nano, gedit etc.
Then we need to create a ".spec" file corresponding to 4.8.6 version, which is should be:

• $WM_THIRD_PARTY/rpmBuild/SPECS/qt-everywhere-opensource-src-4.8.6.spec

This file can be created literally as a copy of of 4.8.5.spec file which should already be in the same folder assuming that you have already set QT_THIRD_PARTY setting to 1. Again, all that needs to be done is to replace the occurrences of 4.8.5 with 4.8.6. This can easily be done using the shell command sed.

For those of you like me who are using devtoolset-2 version gcc which is v4.8.2, ParaView simply refused to compile with it. So I disabled it, and used gcc 4.4.7 which comes with the standard development tools software group of sl6x repo. I'd recommend you to stick with that version instead of a higher one. Make sure you set your compilerInstall=System variable in your prefs.sh.

After that, you can simply source your $WM_PROJECT_DIR/etc/bashrc, execute $WM_THIRD_PARTY/AllMake.stage4 and start the compilation of Qt v4.8.6 which takes a really long time. The script took care of compiling ParaView after finishing its work with Qt v4.8.6, and I got a compiled working version of ParaView v4.0.1 that is compatible with paraFoam.

In attachment I am presenting to you my prefs.sh,and a screenshot of a working ParaView after a painful process .

When I have time, I can try writing out a neat guideline for the process. Thanks again for sharing your experiences and ideas. I'm posting this immediately after getting a successfully compiled ParaView, so I'll post if I encounter further unresolved problems with the entire process of installing foam extend 3.0.

Best regards,