CFD Online Discussion Forums

CFD Online Discussion Forums (http://www.cfd-online.com/Forums/)
-   OpenFOAM Installation (http://www.cfd-online.com/Forums/openfoam-installation/)
-   -   Paraview 3.14.1 + opensuse 12.2 (gcc 4.7.1 & qmake 4.8.1) SOLVED (http://www.cfd-online.com/Forums/openfoam-installation/107406-paraview-3-14-1-opensuse-12-2-gcc-4-7-1-qmake-4-8-1-solved.html)

pcaron September 26, 2012 10:30

Paraview 3.14.1 + opensuse 12.2 (gcc 4.7.1 & qmake 4.8.1) SOLVED
 
1 Attachment(s)
Hello everybody!!!!

I updated my OS to openSUSE 12.2 last weekend. As the title says it comes with gcc 4.7.1 and qt 4.8.1.

I use the reader developed by Takuya Oshima (http://openfoamwiki.net/index.php/Co...r_for_ParaView) The reader requieres that paraview is compiled with some flags (see the previous link for details) so, I use to build paraview by myself instead of use a precompiled version (openSUSE has a Paraview 3.14.0 package)

I found that compile Paraview it is not as straight as it was before, this is because of the gcc version. I found the solution and I want to share it.

In order to build Paraview we have to patch the original sources. The patch file is attached. The patch is a merge from https://build.opensuse.org/package/v...roject=science and http://anonscm.debian.org/gitweb/?p=...c1a34fc103d208

After we patched the sources the compilation follows as before.

Hope it helps somebody!!!!

Pablo

phsieh2005 September 27, 2012 07:57

Hi, Pablo,

It is very nice of you to post the patch.

I have never built paraview (and the OpenFOAM reader). But, now I am using OpenSUSE 12.2 and am having a lot of issues with paraview. So, I would like to give it a try.

After I patched the Paraview source and ran ccmake, I got the following warning:
You are using Qt 4.8.1. Officially supported version is Qt 4.6

Do I need to install Qt4.6? How to install QT 4.6 on OpenSUSE 12.2?

Thanks!

Pei-Ying

phsieh2005 September 27, 2012 08:56

Hi, Pablo,

When I type make to build paraview, it looked like the compilation was successful.

But, when I ran paraview, I got the following error:

hsieh@jali:~/projects/ParaView-3.14.1-Source/ParaView-bin/bin> ./paraview
./paraview: symbol lookup error: ./paraview: undefined symbol: _ZN23pqTabbedMultiViewWidgetC1EP7QWidget
hsieh@jali:~/projects/ParaView-3.14.1-Source/ParaView-bin/bin>
-----------------------------------------------------------------------

Any suggestion?

Pei-Ying
----------------------

[100%] Building CXX object Applications/ParaView/CMakeFiles/paraview-real.dir/moc_ParaViewMainWindow.cxx.o
Linking CXX executable ../../bin/paraview
[100%] Built target paraview-real
Scanning dependencies of target paraview
[100%] Building C object Applications/ParaView/CMakeFiles/paraview.dir/paraview-forward.c.o
Linking C executable launcher/paraview
[100%] Built target paraview
hsieh@jali:~/projects/ParaView-3.14.1-Source/ParaView-bin>

pcaron September 27, 2012 10:58

Hi Pei-Ying

First of all, it feels good to give something back to the community! :D

As you realized, you can compile paraview using qt 4.8.1, the message shown in ccmake it is just a WARNING.

The compile sequence is:
  1. Configure using ccmake utility. It is advisible to use a "build" directory. I use to create a build directory inside paraview-*-Source. So, to configure the compilation, I use ccmake ../
  2. Compile using make utility. Just type make in the build directory
  3. Install paraview using make install. Depending on your installation directory you will need the root password. To keep things clean I use /opt/paraview/3.14.1 directory as installation directory
  4. Add the paraview bin directory to the system PATH. In openSUSE you should create/edit the file /etc/bash.bashrc.local The line to add is: export PATH=$PARAVIEW_DIR/bin:$PATH In my case PARAVIEW_DIR=/opt/Paraview/3.14.1
Did you do the third step? Let me known If this information is useful.


Best,


Pablo

phsieh2005 September 27, 2012 14:50

Hi, Pablo,

Thanks a million!

You were correct. I did not do "make install". I thought that I can run the paraview before installation just to check it out. I was wrong.

I am wondering if you can answer a couple of basic questions because I am not quite sure about the exact steps to build paraview.

1. If I put the source of paraview-3.14 under /opt/paraview/3.14.1, but, the build and install document suggested that paraview should be built in /opt/paraview/3.14.1/paraview-bin (well, in a separate folder in stead of the source), then, what should PARAVIEW_DIR be? PARAVIEW_DIR=/opt/Paraview/3.14.1? or PARAVIEW_DIR=/opt/Paraview/3.14.1/paraview-bin?

2. It looks like paraview-3.14.1 is having issue with reading stl in ascii format. I would like to compile the latest source from svn. After I grab the svn version, I am wondering if I should patch it using your patch? I am hoping that the svn version fixed the issue.

Pei-Ying

pcaron September 27, 2012 15:35

Hi Pei-Ying!

Quote:

Originally Posted by phsieh2005 (Post 383957)
1. If I put the source of paraview-3.14 under /opt/paraview/3.14.1, but, the build and install document suggested that paraview should be built in /opt/paraview/3.14.1/paraview-bin (well, in a separate folder in stead of the source), then, what should PARAVIEW_DIR be? PARAVIEW_DIR=/opt/Paraview/3.14.1? or PARAVIEW_DIR=/opt/Paraview/3.14.1/paraview-bin?

I think I made a mess explaning this step. I will try again.
  1. For the source directory I use one in my home directory. In my case /home/pablo/Programas/Paraview-3.14.1-Source
  2. For the build directory /home/pablo/Programas/Paraview-3.14.1-Source/build
  3. I ran the ccmake from inside the build directory
  4. When configuring I set the variable CMAKE_INSTALL_PREFIX to /opt/Paraview/3.14.1
  5. I ran make, and make install
  6. At this point the system does not known about the paraview binaries, so I added the bin directory to the PATH variable. The PARAVIEW_DIR variable is not really important it is just to add this the directory.
I hope this will be clear now.

Quote:

Originally Posted by phsieh2005 (Post 383957)
2. It looks like paraview-3.14.1 is having issue with reading stl in ascii format. I would like to compile the latest source from svn. After I grab the svn version, I am wondering if I should patch it using your patch? I am hoping that the svn version fixed the issue.



Sorry, I don't know. Try to build the svn version, if it fails try patching the sources, if it still fails...well I don't know.

Best

Pablo

phsieh2005 September 27, 2012 15:45

Thanks a lot Pablo! This really helped.

Pei-Ying

phsieh2005 September 27, 2012 18:35

Hi, Pablo,

I grabbed the latest development version from svn and compilation/installation went through. But, when I ram paraview, I got the following error:

hsieh@jali:~/OpenFOAM/hsieh-2.1.x/run/damBreak> paraview
ERROR: In /home/hsieh/projects/ParaView/VTK/GUISupport/Qt/vtkEventQtSlotConnect.cxx, line 68
vtkEventQtSlotConnect (0x1d0e470): Cannot connect NULL objects.


Segmentation fault
hsieh@jali:~/OpenFOAM/hsieh-2.1.x/run/damBreak>
---------------------------------
Will applying your patch fix this issue? Also, your path applies to ParaView-3.14.1-Source. But, my paraview development version is under $HOME/projects/ParaView. How can I apply your patch to the new folder?

Thanks!

Pei-Ying

phsieh2005 September 28, 2012 07:54

Hi, Pablo,

It looks like there are only 3 files that needed to be patched. So, I did it manually to svn version.

Compilation and installation were successful. But, I still got the same error when I ran paraview.

Thanks!

Pei-Ying

pcaron September 28, 2012 13:51

Hi Pei-Ying

I'm not an expert using patch utility, but googling I found this link
http://www.cyberciti.biz/faq/appy-pa...patch-command/

I think you should look for the solution in vtk and/or paraview forums.

Have a nice weekend!

Pablo

phsieh2005 September 28, 2012 14:59

Hi, Pablo,

Thanks a lot for your help!

Wish you a good weekend too!

Pei-Ying


All times are GMT -4. The time now is 10:29.