Hi boger.

For 'which qmake' I get /usr/bin/qmake. What do you mean by I need 'setenv QT_BIN_DIR /usr. Shall I write it in the console? If yes, I doesn't work. I don t have setenv (opensuse 11.3). I looked for it in the respiratory, but I couldn't find it, nor in the net :(

@pcaron
I know about this issue, I did one week ago. Yesterday, I have downloaded 1.6-ext again and the Allmake.stage4 seems to differ slightly. Correct me if I am wrong.

Cheers
Peter

ok, I figured out that setenv doesn t work for bash shell, so I switched to csh. When I write 'setenv QT_BIN_DIR /usr' in the csh shell nothing happens. Still not able to compile paraview. I checked the last Allmake.stage4 file and indeed it changed. There is now an if statement for the qt files. I do not want to compile it again since I have qt installed on my system. I really don t get it to set environmental variables properly.

I'd go back to your bash shell and add

export QT_BIN_DIR=/usr

to your .bashrc file, which sets the environment variable QT_BIN_DIR. After that, open a new terminal window (to be sure the environment variable gets added) and try your stage4 again. If it doesn't work, please let us know exactly what error message you get.

Out of curiosity, which version of Qt do you have? ("qmake --version" should tell you.)

I still get the same output as before, that the environmental variable QT_BIN_USR is not set properly

my version is:

QMake version 2.01a
Using Qt version 4.6.3 in /usr/lib64

Peter

I'm sorry: try

export QT_BIN_DIR=/usr/bin

Here we go :)
Thank you very much!!!!
Now it s compiling. I let u know about my progress.

Unfortunately an error occurred

Installing 'libQtWebKit4-32bit' solved that problem.

Hi Peter, I agree with you the script is slightly different. I recopiled 1.6-ext yesterday using an updated git version. To enable the ThirdParty Qt, as I did before, you must set a new variable. I typed this before execute stage4 script.
Then I could compile ThirdParty-QT. But you find out how to use the system QT, so I think this info is not relevant now ;)

Regards

Pablo

I have some troubles compiling Openfoam. Which compiler version do u use of gcc. Do you use ur system compiler or one from the ThirdParty package?

cheers
Peter

It is always better to tell us exactly what "troubles" you have run into. Do you get an error message?

Whether or not you can use your system version of gcc probably depends most on what version of gcc you have on your system. What does "gcc --version" tell you?

for foamInstallationTest, I got this


Unfortunately I ve deleted openfoam already. I am going to compile everything again. But it had same warnings concerning paraview, that some variables haven t been set properly.
What is the best way to save the output? when I simply write .Allwmake > log, i don t save all the output from the screen in it. Any suggestions.
Sorry for the poor error message. I will compile it again and change to compiler set by OpenFoam.

Didn't we already discuss this same point in a previous post? The warning you got looks like just that to me - a warning. Based on that warning, there was no reason to delete OpenFOAM.

Maybe it depends on the shell, but something like "Allwmake >& log" or "Allwmake |& tee log" should save the error messages that are written to stderr.

I recompiled everything. OpenFoam is running, paraview and paraFoam,too.
Nevertheless, I am no able to see something when I load a case (icoFoam). In the end of stage4 I got an error. Maybe this could be the reason. I don t know how to treat it..

> Nevertheless, I am no able to see something when I load a case (icoFoam).

This is rather vague....

What is the error message generated by paraview/paraFoam when you load your case?

What is the output of the following command: wmakePrintBuild

Martin

This is my output for 'wmakePrintBuild'
I dont get any error when I open paraview or load a case with paraFoam. I can enter ther GUI of paraview with both cases, but I am not able to see the grid. When I close paraview I get than

Any Idea?

I'm pretty sure this is a bug in glibc. Are you using a gcc-4.5.1 / openSuse combo?

Yes. I am using opensuse 11.3 but gcc gcc-4.5.0.
What is that mean?

Yeah.. It's a general problem with glibc and gcc-4.5.x. The shared libraries aren't unloaded properly by certain class destructors, and so the assertion gets triggered. It doesn't seem to be a major issue, if you're willing to ignore the assertion warning.

I downgraded to gcc-4.4.x, and the problem doesn't exist there. I'll go back up once they fix the issue.

Thank you very much. How can I downgrade my compiler? Just delete this one and install with yast an older one?