CFD Online Discussion Forums

CFD Online Discussion Forums (http://www.cfd-online.com/Forums/)
-   OpenFOAM Paraview & paraFoam (http://www.cfd-online.com/Forums/openfoam-paraview/)
-   -   ParaView / PV3Readers build problem (http://www.cfd-online.com/Forums/openfoam-paraview/93565-paraview-pv3readers-build-problem.html)

bhomer October 19, 2011 09:11

ParaView / PV3Readers build problem
 
4 Attachment(s)
Good morning Bruno,

I am currently using Fedora 14 i686 and you are correct when you say ParaView is installed somewhere else. I followed a suggestion in one of the online discussion threads and used: yum install paraview. It wound up over in the (root) usr/bin directory. My apologies for adding to the confusion here. However I did this after the ParaView build failed as outlined in the attached files.

bhomer

wyldckat October 19, 2011 11:10

Hi bhomer,

Ah Ha! The logs don't lie ;) It seems that you didn't follow the instructions in my blog post! According to the "qtMake.log" file, you didn't execute the command exactly as I wrote down!

Follow (to the letter, if possible) my instructions written here: Building ParaView 3.10.1 with custom Qt 4.6.4
It should all work as intended! If not, post the new logs in your next post :)

Best regards and good luck!
Bruno

PS: for those who might be reading this thread, this all started here: http://www.cfd-online.com/Forums/blo...ml#comment1138

bhomer October 19, 2011 19:23

2 Attachment(s)
Quote:

Originally Posted by bhomer (Post 328582)
Good morning Bruno,

I am currently using Fedora 14 i686 and you are correct when you say ParaView is installed somewhere else. I followed a suggestion in one of the online discussion threads and used: yum install paraview. It wound up over in the (root) usr/bin directory. My apologies for adding to the confusion here. However I did this after the ParaView build failed as outlined in the attached files.

bhomer

Ok, here are the log files form the build. I believe I followed your instructions to the tee.

bhomer

bhomer October 19, 2011 19:25

Quote:

Originally Posted by bhomer (Post 328642)
Ok, here are the log files form the build. I believe I followed your instructions to the tee.

bhomer

I'm sorry I missed one of the files.
bhomer

wyldckat October 20, 2011 03:54

Hi bhomer,

This is odd... "libEGL.so.1" was not found... Try to find it first:
Code:

find /usr/lib -name "libEGL.so*"
find /lib -name "libEGL.so*"

If "libEGL.so.1" is not found... then it's very odd indeed. I don't know Fedora well enough to know in which package is it located in.
But if the file is found, check if the path for it appears in "LD_LIBRARY_PATH":
Code:

echo $LD_LIBRARY_PATH
If it's not, add to it; for example:
Code:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib
Then on the same terminal where you ran the previous command, try building ParaView once more:
Code:

./makeParaView -qmake  ${WM_THIRD_PARTY_DIR}/platforms/$WM_ARCH$WM_COMPILER/qt-4.6.4/bin/qmake > makePV.log 2>&1

wmSET

echo "Are these next two lines the same?"
which paraview
ls $ParaView_DIR/bin/paraview

Best regards,
Bruno

bhomer October 20, 2011 10:30

Good morning Bruno,

Neither find command turned up a "libEGL.so" file. I did an internet search for "Fedora 14 libEGL.so" which tells me there is such a file embedded in MESA. Is this the one I need and, if so, which version of MESA is required?

bhomer

wyldckat October 20, 2011 17:05

Hi bhomer,

My guess is that "libEGL" in your system came from the graphics card drivers. Eitherway, I believe that you can install the necessary Mesa drivers by running as root:
Code:

yum install mesa-libGL-devel
Unfortunately, it might also be necessary to rebuild Qt 4.6.4 after installing Mesa :(


By the way, for a deeper search, you could also try running:
Code:

find / -name "libEGL*"
It'll take longer, but this way you can make sure if such file or similar does exist.

By what I saw now in the VM I've got with Fedora 14 x86_64, it seems that I already have Mesa installed by default (since I'm using a virtual graphics card) and that's probably why I didn't run into these problems.

Best regards and good luck!
Bruno

bhomer October 21, 2011 14:18

2 Attachment(s)
Good morning Bruno, I'm back,

After many trials and tribulations I succeeded in building both Qt and paraview and I got an exact directory match for the which and ls commands. I then followed the directions and built the PV3Readers. I have attached the build log.

When I executed the paraFoam command in the $FOAM_RUN...icoFoam directory I again got a failure although it was different from the one I was getting before. I have attached a log from that execution.

bhomer

P.S. When I finally straightened out the libEGL.so debacle the file wound up in my /usr/local/lib directory.

wyldckat October 21, 2011 17:12

Hi bhomer,

Pardon my French, but... Bloody hell.... I'm starting to get the feeling that only a tire iron would satisfy Fedora's missing dependencies...

OK, the only thing that comes to mind is that there might be something you might have installed in your system that is interfering with the proper compiling and usage of ParaView and/or OpenFOAM.
But fear not, there should be a way for fixing the problem... somehow :confused:

If I had the same problems you are having at the moment, I would try this:
  1. Copy paraFoam to the current case folder:
    Code:

    cp `which paraFoam` .
  2. Check what is the current full path for library searching:
    Code:

    echo $LD_LIBRARY_PATH
  3. Edit the local paraFoam script to add a bit after the first block of comments and before the usage function, the following code (based on the previous output):
    Code:

    #------------------------------------------------------------------------------

    export LD_LIBRARY_PATH=${WM_THIRD_PARTY_DIR}/platforms/$WM_ARCH$WM_COMPILER/paraview-3.10.1/lib/paraview-3.10:${WM_THIRD_PARTY_DIR}/platforms/$WM_ARCH$WM_COMPILER/qt-4.6.4/lib


    usage() {

    In bold is the added line. This will trim down the list of searched paths for the necessary libraries, thus trying to avoid the inclusion of the wrong libraries. The two paths shown are for ParaView and Qt only.
  4. Save the file. Now run the file locally:
    Code:

    ./paraFoam -builtin
    Notice the "./" which points directly to the current folder, instead of calling the original paraFoam script. The "-builtin" tells the script to open the case with the internal reader that comes with ParaView, rather than using OpenFOAM's own reader.
  5. If it crashes with another error, try adding another path from the string at point #2. The path separator is the ":". The paths that you should be testing are the system paths, not OpenFOAM paths per say.
  6. Iterate between the previous 2-3 points until you can figure out if a solution exists or not.
If you manage to figure out the correct setting for point #3, then copy the local paraFoam script back to the place where the original one was:
Code:

cp ./paraFoam `which paraFoam`
Good luck!
Bruno

bhomer October 23, 2011 08:44

Good morning Bruno,

Ok, the error message I'm getting now is:

/home/bhomer/OpenFOAM/ThirdParty-2.0.1/platforms/linuxGcc/paraview-3.10.1/lib/paraview-3.10/paraview: symbol lookup error: /usr/lib/libgconf-2.so.4: undefined symbol: g_bus_get_sync

Which means, if I am interpreting correctly, that a function (g_bus_get_sync) that is supposed to reside in the libgconf-2.so.4 file does not, in fact, do so.

According to an internet search the g_bus_get_sync method is part of the Gnome desktop.

So, my next move is to upgrade Fedora 14 to Fedora 15. If that doesn't work I will install Ubuntu.

Bruno, it's been a real pleasure meeting you and I thank you for all the help you've given me.

bhomer

wyldckat October 23, 2011 08:59

Hi bhomer,

Quote:

Originally Posted by bhomer (Post 329070)
Bruno, it's been a real pleasure meeting you and I thank you for all the help you've given me.

You're welcome :)

If you go to Ubuntu, do not install Ubuntu 11.10 right away. Either install Ubuntu 11.04 (previous version) or 10.04 LTS (Long Term Service). The reasons:
  • Wait at least a month before installing the latest Ubuntu version. There is always some annoying glitch with each release that just won't go away... usually for about a month.
  • There have been some issues with OpenFOAM 2.0 and Ubuntu 11.10, due to some über modern choices made in Gcc and Ld that comes in 11.10: OpenFOAM-2.0.x on Ubuntu 11.10
Best regards and good luck!
Bruno


All times are GMT -4. The time now is 03:52.