Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
New major release with lots of changes. See http://www.paraview.org/New/release.html for details.
Thanks for the heads up, Tim! I hope I can get to it on the weekend. Best, Markus
I had a brief peek at things and it looks to me as if they don't offer any source tarballs for the 3.x branch any more but rather expect people to check things out from their CVS. Can you confirm this? Best, Markus
Yes, unfortunately that is what it looks like. It might help to ask why they don't package source tarballs anymore on their mailing list. Are you subscribed to it?
Strangely enough, at this site http://www.paraview.org/HTML/Download.html they say they offer source tarballs for the latest stable release, but the site is old showing 2.6.1 as the latest stable and 3.0.0 as the latest beta. Perhaps they are hacking too much to find the time to create tarballs ;-). Again, I think a friendly question on their mailing list might help.
Yeah, we should get in touch with them and ask for a source tarball. If you're on their mailing list could you drop them a note? Thanks, Markus
(In reply to comment #5) > Yeah, we should get in touch with them and ask for a source > tarball. If you're on their mailing list could you drop them a note? No problem, I sent a message to the list and am waiting on a reply.
Great, thank you very much!
Here is the response I got: "We can make archives of the source for paraview releases available. I didn't intentionally stop making those, just didn't think of it. We'll create source archives for future releases." Another person suggested to check out the CVS branch for 3.0.2. In the interim, we could pull from the CVS branch, package it ourselves, and release it to the mirrors. Otherwise, we can just wait for the next release and hope someone remembers to package the source.
Thanks Tim! I'd definitely prefer properly versioned source tarballs. Also, I don't want to package the source myself if at all possible, since whatever tarball is floating around the mirrors should also be available from the main paraview SRC_URI. Hence, I suggest we wait for the next release and hope for the best. In the meantime, I'll have a look at the 3.x branch and fix up the ebuild so we can bump to 3.0.3 fairly quickly. Does that sound reasonable? Thanks, Markus
(In reply to comment #9) > Hence, I suggest we wait for the next release and hope for the > best. In the meantime, I'll have a look at the 3.x branch and > fix up the ebuild so we can bump to 3.0.3 fairly quickly. > > Does that sound reasonable? That sounds fine to me. If you want any help with the ebuild just ask. Tim
Hi Tim, Thanks a bunch! I'll leave this bug open untill we've got 3.0.x in portage. Best, Markus
Markus, Etienne L. adapted the existing Paraview ebuild to 3.0.2 and 3.1.0. He sent me a copy of what he did. I plan to take a look at it, test them a bit and then put them here. What do you think? Daniel
Created an attachment (id=125728) [details] Ebuild for 2.6.2 I built it on x86 with nvidia video card (it works) I will build it tonight on my amd64 nvidia I will also test it on my x86 ATI box and see if the old crash is still there.
Sorry my last comment was for #179682 (Paraview 2.6). Somehow things went wrong... ;)
Hi Daniel, A working paraview-3.1.0 ebuild would be great! It looks like the developers have posted the sources for 3.1.0 so this would be a viable candidate to be added to the tree. Thanks, Markus
Created an attachment (id=126446) [details] Ebuild for 3.0.2 Hello Markus, Here is a first attempt for 3.0.2 A few comments: - This is the result of a collaboration with Etienne Lorriaux <etienne.lorriaux@gmail.com> - It needs Qt4 (<4.3.0). It is possible to build the package without support for Qt but then, the frontend ParaView is not build (the rest is there). We flagged Qt4, it could be a dependency as well. The choice is up to you really. - I still have issues with ffmpeg (does not even compile). Etienne does not. - There are a few new flags: boost, xml2. This needs to be tested heavenly - I noticed that I cannot rebuild ParaView over an existing ParaView. I need to emerge -C first and then rebuild. This is very strange. Some problems with some links during the installation phase. - I removed the Cmake 2.2 compatibility flag. That screwed things up. Please test, evaluate, modify... ;)
> - It needs Qt4 (<4.3.0). It is possible to build the package without support > for Qt but then, the frontend ParaView is not build (the rest is there). We > flagged Qt4, it could be a dependency as well. The choice is up to you really. The qt4 USE flag did not work as expected. Although I set the qt4 flag for paraview, emerge did not automatically pull in qt4 as a dependency. It died during compile and complained about having qt version 3.x. Below is the output from emerge showing that it recognized the qt4 flag but did not try to emerge qt4: > [ebuild N ] sci-visualization/paraview-3.0.2 USE="boost python qt4 -doc > -examples -ffmpeg -hdf5 -mpi -threads -xml2" > > Would you like to merge these packages? [Yes/No]
I emerged qt to upgrade from 3.x to 4.3.0-r2 and then emerged paraview. It died with "error: vtk_zlib.h: No such file or directory". I will attach output from emerge --info and relevant portions of build.log.
Created an attachment (id=129640) [details] emerge --info for my second comment
Created an attachment (id=129642) [details] A "cut down" logfile showing error described in my second comment
The line for the qt4 dependency in the ebuild is incorrect. Since we only have qt-4.3.x in portage at the moment this line should simply read qt4? ( >=x11-libs/qt-4.3.0 ) If paraview really need a qt4 version < qt-4.3.0 we'll have to either wait until upstream supports qt-4.3 or come up with a patch to enable it. Best, Markus
I copied the source directory from /usr/portage/distfiles to my home directory and did a local compile successfully, so the missing header error I reported earlier is not an upstream problem. Not sure why that header is missing, but it's probably related to cmake flags. A couple of somewhat-unrelated points: 1. I'm pretty sure tcl and tk are NOT needed for Paraview >=3.0 2. Messing around with ccmake, I see that Paraview builds its own local copy of VTK, which builds its own local zlib, jpeg, etc. We can fix this behavior by setting cmake flags--what do we want to do about this? It reduces redundancy but may add dependencies.
(In reply to comment #22) > 2. Messing around with ccmake, I see that Paraview builds its own local copy of > VTK, which builds its own local zlib, jpeg, etc. We can fix this behavior by > setting cmake flags--what do we want to do about this? It reduces redundancy > but may add dependencies. > The ebuild which Daniel posted already forces paraview to use external libraries rather than building its own which is the preferred behavior, e.g., via DVTK_USE_SYSTEM_ZLIB:BOOL=ON and a dependency on sys-libs/zlibs. This way, important upgrades to libraries propagate to paraview for free rather than us having to patch is own internal implementation which introduces a maintenane nightmare. Markus
Good point about DVTK_USE_SYSTEM_ZLIB:BOOL=ON, perhaps this is why Paraview is looking for a VTK zlib header that does not exist? Is there a Paraview build flag that needs to be set for exernal zlib? I will not be able to look int this until Tuesday because it is on my work computer.
> The ebuild which Daniel posted already forces paraview to use external > libraries > rather than building its own which is the preferred behavior, e.g., via > DVTK_USE_SYSTEM_ZLIB:BOOL=ON and a dependency on sys-libs/zlibs. Yes, that's the way it works. Personally, I don't have this "error: vtk_zlib.h: No such file or directory". However, VTK is installed on my system: ted@paris ~ $ locate vtk_zlib.h /usr/include/vtk-5.0/vtk_zlib.h ted@paris ~ $ equery b /usr/include/vtk-5.0/vtk_zlib.h [ Searching for file(s) /usr/include/vtk-5.0/vtk_zlib.h in *... ] sci-libs/vtk-5.0.3 (/usr/include/vtk-5.0/vtk_zlib.h) This vtk_zlib.h file is also included in the Paraview 3.0.x source code. So, I suspect as Markus mentionned, a Cmake flag issue. Regarding qt-4.3.0, Etienne told me that Paraview 3.0.x did not work well with it. That's why, to begin with, I used qt-4.2.3 The tcl/tk dependency is not needed anymore. It is a 'left-over' of the Paraview 2.x time. I also wanted to check if Paraview 3.x would use tcl/tk is qt was not there. It does not... Daniel
"emerge paraview" is successful if I comment out the line in the ebuild that tells cmake to use the system zlib: # CMAKE_VARIABLES="${CMAKE_VARIABLES} -DVTK_USE_SYSTEM_ZLIB:BOOL=ON" I then un-commented that line and confirmed that the emerge fails in the same way as I previously described. I will use the above as a workaround to test other aspects of Paraview since I don't know what to do about the zlib problem. Should we prevent Paraview from building its own copy of VTK, and add VTK as a dependency?
(In reply to comment #26) > Should we prevent Paraview from building its own copy of VTK, and add VTK as a > dependency? > I don't think this is possible, but if you could come up with a way/patch to do this that would be fantastic. Best, Markus
Markus, unfortunately, it seems that the official distribution of Paraview does not support external libraries and I do not know how to hack it. Instead I will try to find out why it can't find that header file when I use the system zlib. Daniel, I am using qt-4.3 with Paraview 3.0.2 and it works, except that I cannot get the help to work. Instead I get "Failed to start Qt Assistant." Does this work with the older qt-4.2.3 you are using?
(In reply to comment #28) > Daniel, I am using qt-4.3 with Paraview 3.0.2 and it works, except that I > cannot get the help to work. Instead I get "Failed to start Qt Assistant." > Does this work with the older qt-4.2.3 you are using? Craig, thanks for your testing effort. I tested this 'help' function and I get like you, a "Failed to start Qt Assistant." error message. I use qt-4.2.3-r1 Daniel
I'm not sure how this relates precisely, but there is a download site at what appears to be the new paraview website: http://www.paraview.org/New/download.html This still doesn't have a tarball for 3.0, but it DOES have a tarball for the 3.2 beta: http://www.paraview.org/files/v3.2/paraview-3.2.tar.gz Guess I'll have to take a stab at that... About forcing paraview to use external libraries... I understand why one would want that, but in the case of these large scientific applications you might want to be careful about doing so if it's not a supported option from upstream - changes in library behavior might not always be a good thing. In such cases the safer thing to do may be to work with the upstream devs, assuming it is still an active project.
Created an attachment (id=135904) [details] Updated ebuild for Paraview incorporating changes we discussed I built Paraview 3.0.2 successfully on a brand-new system and ran into the same problem with ZLIB. I have attached an ebuild that incorporates the updates we discussed: 1) removed TCL/TK dependencies 2) commented out CMAKE_VARIABLES="${CMAKE_VARIABLES}-DVTK_USE_SYSTEM_ZLIB:BOOL=ON" Paraview 3.0.2 now works fine on two different x86 machines.
Folks, I've just posted an experimental ebuild for paraview-3.2.0 at http://dev.gentoo.org/~markusle/paraview-test/ and you're welcome to give it a shot. It compiles fine for me on x86 but I haven't had time to test it much yet (not sure if help works at all) nor have I tried amd64. ffmpeg and boost currently are a no-go since the former uses a deprecated function call and the latter some strange template instantiation missing from the boost version on my dev box. Hence, both need to be addressed by upstream at some point as far as I can tell. Otherwise, please let me know if you encounter any problems. cheers, Markus
Markus, I am trying your ebuild right now. Did you see that 3.2.1 came out and that it is considered stable? I will 'heavily' modify your ebuild (replacing 3.2 by 3.2.1 ;) ) to see if it works fine. Daniel
Markus, The ebuild for 3.2.0 still contains reference to tcl. Is that really necessary? I wonder. Daniel (In reply to comment #22) > A couple of somewhat-unrelated points: > 1. I'm pretty sure tcl and tk are NOT needed for Paraview >=3.0
Markus, 3.2.0 builds and seems to work correctly on my x86 box. I haven't tested it heavily but I can already say that it seems that the python support has been forgotten (see the menu Tools/Pythonshell). I will now try 3.2.1 Daniel
Two more comments: Any icon in the KDE resp. Gnome menu would be nice... ;) Strange message at the end of the build: Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/lib/paraview-3.2/Documentation/ActiveVariableControlsToolbar.png -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/lib/paraview-3.2/pqClient.adp -- Install configuration: "" -- Install configuration: "" -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/lib/paraview-3.2/libQtTesting.so -- Install configuration: "" -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/lib/paraview-3.2/libpqWidgets.so -- Install configuration: "" -- Install configuration: "" -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/lib/paraview-3.2/libQtChart.so -- Install configuration: "" -- Install configuration: "" -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/lib/paraview-3.2/libpqCore.so -- Install configuration: "" -- Install configuration: "" -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/lib/paraview-3.2/libpqComponents.so -- Install configuration: "" -- Install configuration: "" -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/bin/paraview -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/bin/assistant -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/bin/pvTestDriver -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/lib/paraview-3.2/paraview-real -- Installing /usr/lib/paraview-3.2/libQtCore.so tar: /usr/lib/paraview-3.2: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.2/libQtGui.so tar: /usr/lib/paraview-3.2: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.2/libQtNetwork.so tar: /usr/lib/paraview-3.2: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.2/libQtXml.so tar: /usr/lib/paraview-3.2: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.2/libQtTest.so tar: /usr/lib/paraview-3.2: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /usr/lib/paraview-3.2/libQtAssistantClient.so tar: /usr/lib/paraview-3.2: Cannot chdir: No such file or directory tar: Error is not recoverable: exiting now -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/lib/paraview-3.2/assistant-real -- Install configuration: "" -- Installing /var/tmp/portage/sci-visualization/paraview-3.2.0/image/usr/lib/paraview-3.2/pvTestDriver-real -- Install configuration: "" -- Install configuration: "" -- Install configuration: "" -- Install configuration: "" -- Install configuration: "" -- Install configuration: "" -- Install configuration: "" -- Install configuration: "" >>> Completed installing paraview-3.2.0 into /var/tmp/portage/sci-visualization/paraview-3.2.0/image/
Created an attachment (id=137120) [details] Build for 3.2.0 heavily based on Markus' 3.2.0 Hello Markus, Here is the ebuild I use for 3.2.1. I basically used your 3.2.0 and replaced 3.2 by 3.2.1 (I know, I am a genius... ;) ) Here is what I get: [ 19%] Building CXX object VTK/Rendering/CMakeFiles/vtkRendering.dir/vtkOpenGLPolyDataMapper2D.o [ 19%] Building CXX object VTK/Rendering/CMakeFiles/vtkRendering.dir/vtkOpenGLProperty.o [ 19%] Building CXX object VTK/Rendering/CMakeFiles/vtkRendering.dir/vtkOpenGLRenderWindow.o /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/VTK/Rendering/vtkOpenGLRenderWindow.cxx: In member function `int vtkOpenGLRenderWindow::CreateHardwareOffScreenWindow(int, int)': /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/VTK/Rendering/vtkOpenGLRenderWindow.cxx:1558: error: `DEPTH_STENCIL_EXT' is not a member of `vtkgl' make[2]: *** [VTK/Rendering/CMakeFiles/vtkRendering.dir/vtkOpenGLRenderWindow.o] Error 1 make[1]: *** [VTK/Rendering/CMakeFiles/vtkRendering.dir/all] Error 2 make: *** [all] Error 2 * * ERROR: sci-visualization/paraview-3.2.1 failed. * Call stack: * ebuild.sh, line 1701: Called dyn_compile * ebuild.sh, line 1039: Called qa_call 'src_compile' * ebuild.sh, line 44: Called src_compile * paraview-3.2.1.ebuild, line 128: Called die * The specific snippet of code: * emake -j1 || die "emake failed" * The die message: * emake failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sci-visualization/paraview-3.2.1/temp/build.log'. * This ebuild is from an overlay: '/usr/local/portage/' *
Hi Daniel, Thanks much for your comments and I hope I can update the ebuild for 3.2.1 by tonight. I think you are correct in that tcl is not needed for paraview any more and I think the same applies to java. Looks like we can remove a lot of cruft from the current ebuild :) To build python properly we should probably replace all of what is in the python block now by CMAKE_VARIABLES="${CMAKE_VARIABLES} -DPARAVIEW_ENABLE_PYTHON:BOOL=ON" Cheers, Markus
> cruft from the current ebuild :) To build python properly > we should probably replace all of what is in the python > block now by > CMAKE_VARIABLES="${CMAKE_VARIABLES} -DPARAVIEW_ENABLE_PYTHON:BOOL=ON" The cmake-utils eclass could also be useful to lighten the ebuild.
(In reply to comment #39) > > cruft from the current ebuild :) To build python properly > > we should probably replace all of what is in the python > > block now by > > CMAKE_VARIABLES="${CMAKE_VARIABLES} -DPARAVIEW_ENABLE_PYTHON:BOOL=ON" > > The cmake-utils eclass could also be useful to lighten the ebuild. > Thanks much for the tip! I've though about it in the past but never tried it; it's definitely worth a shot. I've just updated the paraview ebuild to 3.2.1 and posted it at the link in comment 32. The tcl and java deps are gone and python now seems to work as expected. I also fixed the issues that Daniel reported in comment 36 I believe. Please test. Thanks, Markus
Markus, A few comments: - The MY_PV variable was still set to 3.2. I changed it to 3.2.1 to test Paraview 3.2.1 (In the meantime I renamed the patches as well) - I ended up with... :( [ 16%] Building CXX object VTK/Rendering/CMakeFiles/vtkRendering.dir/vtkOpenGLPainterDeviceAdapter.o [ 16%] Building CXX object VTK/Rendering/CMakeFiles/vtkRendering.dir/vtkOpenGLPolyDataMapper.o [ 16%] Building CXX object VTK/Rendering/CMakeFiles/vtkRendering.dir/vtkOpenGLPolyDataMapper2D.o [ 16%] Building CXX object VTK/Rendering/CMakeFiles/vtkRendering.dir/vtkOpenGLProperty.o [ 16%] Building CXX object VTK/Rendering/CMakeFiles/vtkRendering.dir/vtkOpenGLRenderWindow.o /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/VTK/Rendering/vtkOpenGLRenderWindow.cxx: In member function `int vtkOpenGLRenderWindow::CreateHardwareOffScreenWindow(int, int)': /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/VTK/Rendering/vtkOpenGLRenderWindow.cxx:1558: error: `DEPTH_STENCIL_EXT' is not a member of `vtkgl' make[2]: *** [VTK/Rendering/CMakeFiles/vtkRendering.dir/vtkOpenGLRenderWindow.o] Error 1 make[1]: *** [VTK/Rendering/CMakeFiles/vtkRendering.dir/all] Error 2 make: *** [all] Error 2 I try now the new ebuild with 3.2.0 Daniel
Markus, The problems I mentionned yesterday have been apparently solved for Paraview 3.2.0. Great job! ;) BTW, do you know that the sunrise overlay contains a fairly advanced ebuild for OpenFOAM (see http://bugs.gentoo.org/show_bug.cgi?id=104257)? Oliver took care of it and did a great job. Two comments on it: - It relies on the Paraview 2.6.2 ebuild we made (2.6.2 had a strange bug though, if I recall correctly) - The ebuild in itself reconstructs Paraview if Paraview is not installed on a system (by using part of our ebuild which is cool...) So, The Paraview 2.6.2 ebuild might gain of the maturity acquired while writing the 3.x serie and could be officialized, to make sure OpenFOAM has something to bite on. What do you think? Daniel
Hello Daniel, thanks a lot for the ebuild. Could you please also provide the patches used there, paraview-3.2.1-support-qt4.3.patch and paraview-3.2.1-libxml2-fix.patch? Thanks a lot - Eckard
Created an attachment (id=137228) [details] ebuild for paraview-3.2.1
Created an attachment (id=137230) [details] libxml2 patch for paraview-3.2.1.ebuild
Created an attachment (id=137232) [details] QT4 fixes for paraview-3.2.1.ebuild
Folks, I've just posted my latest paraview-3.2.1 ebuild plus patches. I did a lot of cleanup and prevented paraview to install a whole bunch of duplicate QT4 libraries. Please test them and let me know of any problems. Thanks, Markus
Looks like 3.2.1 has a regression since I currently get the same error that Daniel reported in #37. I'll see if I can fix it. Best, Markus
(In reply to comment #48) > Looks like 3.2.1 has a regression since I currently get the same error > that Daniel reported in #37. I'll see if I can fix it. > > Best, > Markus > Thanks Markus, i've successfully compiled (manually, without ebuild) paraview 3.2.1, but i had to install qt-4.2.3 in /usr/local. I'm currently testing your ebuild with the qt-4.3 patch. The first try returns effectively the same error. But commenting lines 59-60 and 70-75, it seems to work fine. It's currently building, i hope it will go to end...
Created an attachment (id=137267) [details] small fixes for posted paraview-3.2.1.ebuild This patch should fix a small bug in the previously posted paraview-3.2.1.ebuild and should also fix the vtkGl issue. Using it, I've just successfully built paraview-3.2.1. Best, Markus
Hello Markus, Paraview 3.2.1 builds and seems to work here (x86). Here is what I used: Python 2.4.4 (#1, Nov 19 2007, 09:58:56) [GCC 3.4.6 (Gentoo 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10)] on linux2 Very good job! Daniel
Using the latest ebuild, I'm getting the following: [ebuild N ] sci-visualization/paraview-3.2.1 USE="doc examples hdf5 python qt4 threads -mpi" [ 72%] Built target qtimageviewer gmake[5]: Entering directory `/var/tmp/portage/sci-visualization/paraview-3.2.1/ work/build/VTK/Examples/All' Linking CXX executable /var/tmp/portage/sci-visualization/paraview-3.2.1/work/bu ild/bin/qtsimpleview CMakeFiles/qtsimpleview.dir/main.o: In function `main': main.cxx:(.text+0xc3): undefined reference to `QApplication::setMainWidget(QWidg et*)' collect2: ld returned 1 exit status gmake[5]: *** [/var/tmp/portage/sci-visualization/paraview-3.2.1/work/build/bin/ qtsimpleview] Error 1 gmake[5]: Leaving directory `/var/tmp/portage/sci-visualization/paraview-3.2.1/w ork/build/VTK/Examples/All' gmake[4]: *** [GUI/Qt/SimpleView/CMakeFiles/qtsimpleview.dir/all] Error 2 gmake[4]: Leaving directory `/var/tmp/portage/sci-visualization/paraview-3.2.1/w ork/build/VTK/Examples/All' gmake[3]: *** [all] Error 2 gmake[3]: Leaving directory `/var/tmp/portage/sci-visualization/paraview-3.2.1/w ork/build/VTK/Examples/All' make[2]: *** [VTK/VTKExamples] Error 1 make[1]: *** [VTK/Examples/CMakeFiles/VTKExamplesTarget.dir/all] Error 2 make: *** [all] Error 2 * * ERROR: sci-visualization/paraview-3.2.1 failed. * Call stack: * ebuild.sh, line 1701: Called dyn_compile * ebuild.sh, line 1039: Called qa_call 'src_compile' * ebuild.sh, line 44: Called src_compile * paraview-3.2.1.ebuild, line 125: Called die * The specific snippet of code: * emake -j1 || die "emake failed" * The die message: * emake failed * * If you need support, post the topmost build error, and the call stack if rele vant. * A complete build log is located at '/var/tmp/portage/sci-visualization/paravi ew-3.2.1/temp/build.log'. * This ebuild is from an overlay: '/usr/local/portage/' * I have qt-4.3.2 installed with the following flags: [ebuild R ] x11-libs/qt-4.3.2 USE="cups doc gif jpeg opengl png sqlite sqlite3 ssl zlib -accessibility -dbus -debug -examples -firebird -glib -mng -mysql -nas -nis -odbc -pch -postgres -qt3support -tiff -xinerama" INPUT_DEVICES="-wacom"
Cliff, Please try re-emerging qt4 with USE="qt3support" which may be neccessary (if so, I will enforce it in the ebuild). Alse, when re-emerging paraview could you please do VERBOSE=true /usr/bin/emerge paraview which will provide more verbose output. Thanks, Markus
That was it - needed qt3support built in. Build succeeded, thanks guys!
Great and thanks for the update! I'll add a test for qt3support to the ebuild. After making sure that all is well on my amd64 dev box I'll commit the ebuild to portage. Thanks, Markus
(In reply to comment #55) > Great and thanks for the update! I'll add a test for qt3support to > the ebuild. > After making sure that all is well on my amd64 dev box I'll commit > the ebuild to portage. > > Thanks, > Markus > It compiles fine, but i'm still getting problems when installing : CMake Error: Error in cmake code at /var/tmp/portage/sci-visualization/paraview-3.2.1/work/build/Applications/Client/cmake_install.cmake:39: FILE INSTALL cannot find file "/usr/bin/assistant" to install. Current CMake stack: [3] /var/tmp/portage/sci-visualization/paraview-3.2.1/work/build/Applications/Client/cmake_install.cmake [2] /var/tmp/portage/sci-visualization/paraview-3.2.1/work/build/Applications/cmake_install.cmake [1] /var/tmp/portage/sci-visualization/paraview-3.2.1/work/build/cmake_install.cmake make: *** [install] Erreur 255 [31;01m*[0m [31;01m*[0m ERROR: sci-visualization/paraview-3.2.1 failed. [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 1701: Called dyn_install [31;01m*[0m ebuild.sh, line 1138: Called qa_call 'src_install' [31;01m*[0m ebuild.sh, line 44: Called src_install [31;01m*[0m paraview-3.2.1.ebuild, line 131: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m make DESTDIR="${D}" install || die "make install failed" [31;01m*[0m The die message: [31;01m*[0m make install failed [31;01m*[0m [31;01m*[0m If you need support, post the topmost build error, and the call stack if relevant. [31;01m*[0m A complete build log is located at '/var/tmp/portage/sci-visualization/paraview-3.2.1/temp/build.log'. [31;01m*[0m This ebuild is from an overlay: '/usr/local/portage/' [31;01m*[0m I don't have this problem with the CVS version... I'll try to apply qt-4.3 patches to the CVS version...
Hi Etienne, Thanks for the heads up! Just to make sure, you are using the most recent version of the qt4.3 patch as posted above? Also, the error message indicates that you are missing /usr/bin/assistant which is owned by qt4. Could you please confirm that is is present on your system. Best, Markus
(In reply to comment #57) > Hi Etienne, > > Thanks for the heads up! Just to make sure, you > are using the most recent version of the qt4.3 patch as > posted above? Also, the error message indicates that > you are missing /usr/bin/assistant which is owned > by qt4. Could you please confirm that is is present on > your system. > > Best, > Markus > Hi Markus, effectively, i don't have /usr/bin/assistant. I was thinking that it was a difference between qt-4.2 and qt-4.3. I have qt-4.3.2 installed with the following USE flags : cups gif jpeg opengl png qt3support ssl tiff -accessibility -dbus -debug -doc -examples -firebird -glib -input_devices_wacom -mng -mysql -nas -nis -odbc -pch -postgres -sqlite -sqlite3 -xinerama -zlib I'll try to reemerge qt-4.3.2... Thanks Markus
Hi Etienne, It is possible that qt4 needs USE="doc" to build assistant but I haven't tested it yet. Maybe give this a try if a simple re-emerging won't do and we can force this USE flag in the paraview ebuild. Markus
(In reply to comment #59) > Hi Etienne, > > It is possible that qt4 needs USE="doc" to build assistant > but I haven't tested it yet. Maybe give this a try if a > simple re-emerging won't do and we can force this USE > flag in the paraview ebuild. > > Markus > Hi Markus, a simple re-emerge solved the problem for /usr/bin/assistant. The build works, but when i start paraview, all the widgets are grey... I'm wondering if other people have the same problem or if their paraview build works correctly. Etienne.
Etienne, I did not notice any issue with widget/colors. Daniel PS: Are you aware that Oliver has created an ebuild for OpenFOAM? It's in sunrise
Created an attachment (id=137708) [details] updated patch The above patch adds a check for qt3support in qt4 to the previously posted patch.
(In reply to comment #60) > a simple re-emerge solved the problem for /usr/bin/assistant. The build works, > but when i start paraview, all the widgets are grey... I'm wondering if other > people have the same problem or if their paraview build works correctly. Hi Etienne, I am not quite sure what you mean by "all widgets are grey". Could you maybe give a concrete example? In any case, this sounds more like you are having issues with Qt4. Do other Qt4 applications work properly (like assistant, designer) and have you tried playing around with qtconfig? Thanks, Markus
on amd64: well, i've just installed sci-visualization/paraview-3.2.1 USE="doc examples python qt4 threads -hdf5 -mpi" and it seems to be fine after a first glance at least. also note, that i manually removed "-j1" in the ebuild and didn't run into any problems (build it two times) on an Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz with "-j3". thanks for your efforts! paraview-3.2.1 will see some further testing by me and my colleagues in the next few days. should we encounter any serious problems, they will be reported here.
I've tried to emerge paraview-3.2.1, but compilation failed. Any suggestions? [ 24%] Building C object Utilities/hdf5/CMakeFiles/vtkhdf5.dir/H5Zdeflate.o /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c: In function 'H5Z_filter_deflate': /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:83: error: 'z_stream' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:83: error: (Each undeclared identifier is reported only once /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:83: error: for each function it appears in.) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:83: error: expected ';' before 'z_strm' /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:91: error: 'z_strm' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:93: error: 'uInt' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:93: error: expected ';' before '_tmp_overflow2' /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:93: error: expected ')' before '_tmp_overflow' /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:93: error: '_tmp_overflow2' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:95: error: expected ';' before '_tmp_overflow2' /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:95: error: expected ')' before '_tmp_overflow' /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:98: error: 'Z_OK' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:104: error: 'Z_SYNC_FLUSH' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:107: error: 'Z_STREAM_END' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:150: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:150: error: 'z_src' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:150: error: expected ')' before 'Bytef' /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:151: error: 'Bytef' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:151: error: 'z_dst' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:152: error: 'uLongf' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:152: error: expected ';' before 'z_dst_nbytes' /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:153: error: 'uLong' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:153: error: expected ';' before 'z_src_nbytes' /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:160: error: 'z_dst_nbytes' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:164: error: 'z_src_nbytes' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:167: error: 'Z_BUF_ERROR' undeclared (first use in this function) /var/tmp/portage/sci-visualization/paraview-3.2.1/work/ParaView3.2.1/Utilities/hdf5/H5Zdeflate.c:169: error: 'Z_MEM_ERROR' undeclared (first use in this function) make[2]: *** [Utilities/hdf5/CMakeFiles/vtkhdf5.dir/H5Zdeflate.o] Error 1 make[1]: *** [Utilities/hdf5/CMakeFiles/vtkhdf5.dir/all] Error 2 make: *** [all] Error 2
(In reply to comment #65) > I've tried to emerge paraview-3.2.1, but compilation failed. Any suggestions? > Please provide "emerge -pv paraview" as well as "emerge --info". Thanks, Matthias
gandalf ~ # emerge -pv paraview These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] sci-visualization/paraview-3.2.1 USE="doc examples python qt4 -hdf5 -mpi -threads" 0 kB [1] Total: 1 package (1 new), Size of downloads: 0 kB Portage tree and overlays: [0] /usr/portage [1] /usr/portage/local/layman/science gandalf ~ # emerge --info Portage 2.1.3.19 (default-linux/x86/2006.1/desktop, gcc-4.1.2, glibc-2.6.1-r0, 2.6.22-suspend2-r1 i686) ================================================================= System uname: 2.6.22-suspend2-r1 i686 Intel(R) Pentium(R) M processor 1400MHz Timestamp of tree: Tue, 04 Dec 2007 04:46:01 +0000 app-shells/bash: 3.2_p17 dev-java/java-config: 1.2.11-r1 dev-lang/python: 2.4.4-r7, 2.5.1-r4 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.9-r2 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.22-r2 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium-m" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-O2 -march=pentium-m" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp.rz.tu-bs.de/pub/mirror/ftp.gentoo.org/gentoo-distfiles/" LINGUAS="ru" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/science /usr/portage/local/layman/sunrise" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X aac acpi alsa arts bash-completion berkdb bitmap-fonts blas boehm-gc browserplugin bzip2 cairo cdr cli cracklib crypt css cups curl dbus doc dri dvd dvdr dvdread eds emacs emboss encode esd fam ffmpeg fftw firefox fltk fortran gd gdbm gif gmp gnome gpm gsl gstreamer gtk hal iconv imagemagick isdnlog jpeg kde lapack latex ldap leim mad midi mikmod mozilla mp3 mpeg mudflap mule ncurses nls nptl nptlonly nsplugin offensive ogg opengl openmp oss pam pcre pdf perl plotutils png ppds pppd python qt3 qt4 quicktime readline reflection sdl session speex spell spl ssl tcl tcpd tetex tk truetype truetype-fonts type1-fonts umfpack unicode vcd vorbis win32codecs wxwindows x86 xine xml xorg xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="ru" USERLAND="GNU" VIDEO_CARDS="i810 vesa fbdev" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #67) > gandalf ~ # emerge -pv paraview > > > Calculating dependencies... done! > [ebuild N ] sci-visualization/paraview-3.2.1 USE="doc examples python qt4 > -hdf5 -mpi -threads" 0 kB [1] > hmm, i cannot reproduce this; for me paraview-3.2.1 can be successfully installed with exactly these USE flags, although on amd64. i should have the opportunity to try the same on an x86 box tomorrow. maybe it's reproducible there...
I have no problems on x86 with hdf5 (both 1.6.4 and 1.6.6 work fine). Could you please try re-emerging zlib and hdf5 and please post what version and useflags of hdf5 you are using. Finally, when you try re-emerging paraview could you please pass VERBOSE=true on the command line so I can see what flags cmake uses to compile H5Zdeflate.c? Thanks, Markus
I have hdf5-1.6.4 gandalf ~ # equery u hdf5 [ Searching for packages matching hdf5... ] [ Colour Code : set unset ] [ Legend : Left column (U) - USE flags from make.conf ] [ : Right column (I) - USE flags packages was installed with ] [ Found these USE variables for sci-libs/hdf5-1.6.4 ] U I - - debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see http://www.gentoo.org/proj/en/qa/backtraces.xml . - - hlapi : Enables support for high-level library - - mpi : Adds MPI (Message Passing Interface) layer to the apps that support it. + + ssl : Adds support for Secure Socket Layer connections - - static : !!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically + + szip : Use the szip compression library - - threads : Adds threads support for various packages. Usually pthreads + + zlib : Adds support for zlib (de)compression I thought that the problem may be caused by the USE flag hlapi not set. So, I decided to upgrade hdf5 to 1.6.6 (this version does not have this use flag). But I failed: >>> Compiling source in /var/tmp/portage/sci-libs/hdf5-1.6.6/work/hdf5-1.6.6 ... configure: error: invalid package name: pic --enable-shared --disable-cxx --enable-production * * ERROR: sci-libs/hdf5-1.6.6 failed. * Call stack: * ebuild.sh, line 1701: Called dyn_compile * ebuild.sh, line 1039: Called qa_call 'src_compile' * ebuild.sh, line 44: Called src_compile * hdf5-1.6.6.ebuild, line 126: Called die * The specific snippet of code: * ./configure --prefix=/usr "${myconf}" \ * $(use_enable zlib) \ * $(use_with ssl) \ * --enable-linux-lfs \ * --sysconfdir=/etc \ * --infodir=/usr/share/info \ * --libdir=/usr/$(get_libdir) \ * --mandir=/usr/share/man || die "configure failed" * The die message: * configure failed
I think you've hit a problem with hdf5-1.6.6 that I fixed a few days ago. Please re-sync your tree and try again. Markus
on x86: sci-libs/hdf5-1.6.4 USE="ssl threads zlib -debug -hlapi -mpi -static -szip" sci-visualization/paraview-3.2.1 USE="examples hdf5 python qt4 threads -doc -mpi" can be installed without any problems for me and i can confirm that at least sci-visualization/paraview-3.2.1 USE="doc examples python qt4 threads -hdf5 -mpi" seems to work well either. Andrey, are you still having problems with hdf5? If not, i don't see any reason why this ebuilds should not hit the tree soon...
Folks, I just committed the paraview-3.2.1 ebuild to portage since things seem to work smoothly for most people. I've also removed the -j1 from emake since parallel make works fine for me and we can always put it back if people start having problems compiling - otherwise the extra CPU processes might come in handy. Thanks to everybody for testing and helping out. Please file new bugs should there be any problems. cheers, Markus
Created an attachment (id=138784) [details] OpenFOAM Reader patch To activate the build in capabilities of Paraview for OpenFOAM Files, this patch is needed at compile time. Maybe this can be activated with an USE Flag, so that my ebuild from bug 104257 has an postprocessing tool. The built-in capabilities of Paraview were selected as default in version 2.6.2.
Created an attachment (id=138785) [details] Patch for the OpenFOAM Reader This patch improves the built-in capabilities from Paraview for the OpenFOAM Datastructure very much. I would highly recommend to add this patch to the ebuild, if the openfoam support is compiled with.
Since the update to version 3.2.1 of Paraview I'm not able to use the native OpenFOAM Readers in Paraview. So please add the above patches to the ebuild. Thank's!
Hi Oliver, Thanks much for your patches. Please file a new bug for this with a descriptive summary like "paraview-3.2: add OpenFoam support" so we can track issues and bugs more easily. This bug is closed and I may forget about it ;) cheers, Markus
