Bugzilla Bug 118130

very nice visualization program based on VTK

http://paraview.org/
"an application designed with the need to visualize large data sets in mind.
The goals of the ParaView project include the following: 
Develop an open-source, multi-platform visualization application.
Support distributed computation models to process large data sets.
Create an open, flexible, and intuitive user interface.
Develop an extensible architecture based on open standards.
ParaView runs on distributed and shared memory parallel as well as single
processor systems"

basically it has now dependancy on VTK, since it included in source. but if
somebody separate them it would be great. there is no reason to keep extra vtk
library.

This bug shuld be probably reassigned to sci.
See also discussin on:
http://www.archivum.info/gentoo-science@lists.gentoo.org/2005-12/msg00021.html

I am interested in this package, I will try to install and test it, if it is
good for me, I might even take it as maintainer.

cmake is a tough bugger, there is problems in the makefile, we should wait
until 2.5.x comes out and be stabilized. Maybe fixed in 2.4.4 ??? At least I
have seen the problem on amd64 and few other by googling around. the x86 32bit
should work as normal... but I can't test it now.

Philippe,

Je peux l'essayer.
I have two machines at my disposal here:
AMD64 gcc 3.4.5, glibc 2.3.6
x86 gcc 4.1.1, glibc 2.4.0

I am very much willing to test the ebuild and report any problem / success /
issues related to it.

Paraview depends on vtk and indeed, there is no need to have twice the library
installed (same kind of 'niceties' with OpenFOAM (http://www.openfoam.org)
which depends on lam-mpi)
vtk depends also on mpich (MPI implementation) also.
The problem with mpich is that it cannot cohexist with lam-mpi, but that's an
other issue.

Please, send me the latest ebuild, I will test it and report here.

Cordialement,

Daniel

Created an attachment (id=92640) [edit]
First attempt for a Paraview ebuild

Need to be heavily tested. It is defintely perfectible...
I need help with the documentation part
This ebuild is based on the VTK 5.0.1 one. However, I did not understand
everything on that ebuild....
Otherwise the binary is built and seems to be working.
As I said: testing, testing, testing... ;)

Hello,

Here was my first attempt for the ebuild.
It is far away from perfect... It takes ages to build and to be honest, I have
troubles to generate and store the documentation. There any help is welcome...

I have been defining a few flags (emerge -pv paraview to see them).
The compilation parts works on my x86 box. The binary seems to be working as
well. The only thing that prevented me from installing the final package on my
system were issues with the documentation...

Please feel free to give it a try, and to help me to make it even better... ;)

Enjoy!

Daniel

*** Bug 141876 has been marked as a duplicate of this bug. ***

Created an attachment (id=98919) [edit]
A second attempt to an ebuild

This is a second attempt. The problem I had previously with the sandbox
disappeared mysteriously.
This time I am using Cmake 2.4.3 (6 Oct 2006 today) instead of 2.2.3
This is very weird...

In any case, please test this ebuild and report any problem here. It is still
uncomplete (especially with regards to documentation, I think) but Paraview
seems to work (the demo works at least...).

Enjoy!

Created an attachment (id=98920) [edit]
patch 1

Created an attachment (id=98921) [edit]
patch 2

Hello,

I have tested a little bit further what could have been the cause of the
problem I encountered (The package built correctly but files were installed at
the wrong place and portage generated a sandbox error)
- Cmake 2.2.3 caused the problem
- Cmake 2.4.2 caused the problem
- Cmake 2.4.3 does not cause the problem, apparently. 

Created an attachment (id=99040) [edit]
A few corrections

Hello,

I added to the ebuild the correction on cmake (has to be 2.4.3 at least), and
the support to amd64 (it builds and seems to run fine on this architecture.

I consider this ebuild ready for mainstream. 

(In reply to comment #8)
> 
> In any case, please test this ebuild and report any problem here. It is still
> uncomplete (especially with regards to documentation, I think) but Paraview
> seems to work (the demo works at least...).
> 

Hi Daniel, 

I did some more testing today and the paraview ebuild looks pretty fine
to me. Could you elaborate on what's still missing from your point of view!
In terms of documentation I don't see much in the source tarball
beyond what we have already.

Thanks,
Markus

I agree with you. I think the ebuild is complete now. My comment about
documentations was based on the recollection I had of the early ebuilds. I
think everything is there now.

(In reply to comment #14)
> I agree with you. I think the ebuild is complete now. My comment about
> documentations was based on the recollection I had of the early ebuilds. I
> think everything is there now.
> 

Nice! I'll add paraview to portage in the next few days, probably package
masked so it can be tested some more.

Thanks,
Markus

(In reply to comment #15)
> Nice! I'll add paraview to portage in the next few days, probably package
> masked so it can be tested some more.
> 
> Thanks,
> Markus
> 

Paraview is in portage now :) Currently, it is package.masked for a 
bit more testing. Please give it a spin and report back should there
be any problems. If not, I'll unmask it soon.

Thanks,
Markus

Created an attachment (id=100282) [edit]
An improved ebuild

Added support to the threads and ffmpeg flags 

Hello,

I noticed something strange. It seems like this ebuild, somehow, does not like
revdep-rebuild...
If I type revdep-rebuild with Paraview installed with this ebuild, the system
complain that the executable has troubles with many of its own libraries. In
practice though, Paraview works very well... Strange...

BTW, What about an Icon in the KDE and Gnome menus?
I don't know how to do that but I don't think it is so complicated...

Markus, can you fix that?

Daniel

> I noticed something strange. It seems like this ebuild, somehow, does not like
> revdep-rebuild...
> If I type revdep-rebuild with Paraview installed with this ebuild, the system
> complain that the executable has troubles with many of its own libraries. In
> practice though, Paraview works very well... Strange...
> 

same for me - but revdep-rebuild doesn't like gcc either if compiled with "gcj"
...

revdep-rebuild uses ldd as far as i know; and according to ldd revdep-rebuild
is right; however, what revdep-rebuild does not know (and can't know i guess)
is that
paraview seems to add "/usr/lib/paraview/" the to the library path while
startig up ...

Folks,

I've just updated the ebuild and all of the shared objects
should now be found and revdep-rebuild be happy (at least
on my dev box). Please give it a shot (once the updated ebuild
has hit the mirrors) and don't forget to "source /etc/profile" if you
are starting paraview inside an already running shell.
Please let me know if anything breaks.

Thanks,
Markus

Hello,

I have just rebuild paraview with the new ebuild. Everything went fine.
I have tested the revdep-rebuild. There is still a minor issue

broken /usr/bin/pvpython (requires  libvtkPVServerCommonPython.so
libvtkPVServerManagerPython.so)

IMHO, besides the little problem mentionned above, the only thing missing now
is a link in the menus (Gnome, KDE) and maybe a little icon. Then everything is
fine and I think the ebuild can go mainstream.

I heard the ParaView 3.0 (Qt based) is not so far away, so I think we need to
have 2.4.4 out now.

Daniel

(In reply to comment #23)
> Hello,
> 
> I have just rebuild paraview with the new ebuild. Everything went fine.
> I have tested the revdep-rebuild. There is still a minor issue
> 
> broken /usr/bin/pvpython (requires  libvtkPVServerCommonPython.so
> libvtkPVServerManagerPython.so)

The pvpython on my dev box does not link against these libraries.
Could you please post the output of "ldd /usr/bin/pvpython" as well
as the libraries that are installed by paraview into /usr/lib/paraview-2.4
or better even, post the output of equery f paraview, but maybe as an 
attachment since it is a fairly long list.

Thanks in advance

> 
> IMHO, besides the little problem mentionned above, the only thing missing now
> is a link in the menus (Gnome, KDE) and maybe a little icon. Then everything is
> fine and I think the ebuild can go mainstream.

An executable that doesn't start up due to missing shared object is a pretty
major issue, imho :)

Thanks,
Markus

in reply to comment #23 and comment #24:

> broken /usr/bin/pvpython (requires  libvtkPVServerCommonPython.so
> libvtkPVServerManagerPython.so)

it's the same for me on two boxes x86 with
paraview-2.4.4  USE="examples python threads -doc -ffmpeg -hdf5 -mpi"
/
paraview-2.4.4  USE="doc examples ffmpeg python threads -hdf5 -mpi"

at least on the second box, i can confirm that paraview works at least
basically (i've only ssh access to the second one currently).

> Could you please post the output of "ldd /usr/bin/pvpython" as well
> as the libraries that are installed by paraview into /usr/lib/paraview-2.4
> or better even, post the output of equery f paraview, but maybe as an 
> attachment since it is a fairly long list.

attachments will follow ...

Created an attachment (id=102505) [edit]
<|mlangc|> ldd /usr/bin/pvpython

ldd /usr/bin/pvpython as requested for 
paraview-2.4.4  USE="doc examples ffmpeg python threads -hdf5 -mpi"
on

Portage 2.1.1-r2 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.4-r4,
2.6.18-gentoo-r2 i686)
=================================================================
System uname: 2.6.18-gentoo-r2 i686 AMD Athlon(tm) XP 2400+
Gentoo Base System version 1.12.6
Last Sync: Tue, 21 Nov 2006 10:50:01 +0000
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632)
[disabled]
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.3.7, 2.0.30
dev-lang/python:     2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r4
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.17-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=athlon-xp -O2 -pipe"
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/env.d/java/ /etc/gconf
/etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c"
CXXFLAGS="-march=athlon-xp -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig collision-protect distlocks metadata-transfer sandbox
sfperms strict"
GENTOO_MIRRORS="ftp://ftp.sh.cvut.cz/MIRRORS/gentoo/gentoo "
LANG="en_US.utf8"
LC_ALL="en_US.utf8"
LINGUAS="en de"
MAKEOPTS="-j2"
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'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://192.168.0.1/gentoo-portage"
USE="x86 3dnow 3dnowext X a52 aac acpi aiglx alsa audiofile beagle berkdb
bitmap-fonts bzip2 cairo cdr cli cracklib crypt css cups dbus dlloader dri dvd
dvdr dvdread eds elibc_glibc emboss encode evo exif fam fbcon ffmpeg firefox
flac fortran gdbm gif ginac gmp gnome gphoto2 gpm gstreamer gtk gtk2 hal howl
iconv icq input_devices_keyboard input_devices_mouse ipv6 isdnlog java
javascript jpeg jpeg2k kernel_linux lcms ldap libg++ linguas_de linguas_en mad
mikmod mime mmx mmxext mono mozsvg mp3 mpeg msn nautilus ncurses nfs nls nptl
nptlonly nsplugin nvidia offensive ogg oggvorbis opengl pam pcre perl plotutils
png posix ppds pppd python qt3 qt4 quicktime readline real reflection ruby sdl
session sockets spell spl sqlite3 sse ssl subtitles svg tcpd tetex theora
threads tiff truetype truetype-fonts type1-fonts udev unicode usb userland_GNU
vcd video_cards_nvidia vorbis win32codecs wma xine xml xorg xv xvid zlib"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS,
PORTAGE_RSYNC_EXTRA_OPTS

Created an attachment (id=102506) [edit]
<|mlangc|> equery files paraview

same box, same USE as in comment #26

Hello,

Here is what you required. Few comments: Paraview seems to work (the demo works
at least), on x86 as well as on amd64.
I send the information you asked from one of my x86 boxes. Tonight I can do the
same from the amd64 box if necessary. Just tell me.

sci-visualization/paraview-2.4.4  USE="doc ffmpeg hdf5 python threads -examples
-mpi"

Daniel

Created an attachment (id=102517) [edit]
equery -f paraview on my x86 box

Created an attachment (id=102518) [edit]
ldd pvpython on my x86 box

(In reply to comment #30)
> Created an attachment (id=102518) [edit]
> ldd pvpython on my x86 box
> 

Thanks to all for the files! I'll try to have a look at them asap
to see what is going on. However, since this week is Thanksgiving
here in the US I probably won't be able to get much done until
Sunday - so bear with me:)

best,
Markus 

Created an attachment (id=102909) [edit]
force install of libraries needed for pvpython

Hi all,

Could you please give the attached patch a spin and see if pvpython
now finds all its dependent libraries! In other words, an "ldd pvpython" should 
now find all needed so's. 

Thanks,
Markus

It did the trick...

ldd ./pvpython
        linux-gate.so.1 =>  (0xffffe000)
        libvtkPVServerManagerPython.so =>
/usr/lib/paraview-2.4/libvtkPVServerManagerPython.so (0xb7e21000)
        libvtkCommon.so.pv2.4 => /usr/lib/paraview-2.4/libvtkCommon.so.pv2.4
(0xb7ca7000)
        libvtkFiltering.so.pv2.4 =>
/usr/lib/paraview-2.4/libvtkFiltering.so.pv2.4 (0xb7a55000)
        libvtkIO.so.pv2.4 => /usr/lib/paraview-2.4/libvtkIO.so.pv2.4
(0xb7755000)
        libvtkGraphics.so.pv2.4 =>
/usr/lib/paraview-2.4/libvtkGraphics.so.pv2.4 (0xb71c5000)
        libvtkImaging.so.pv2.4 => /usr/lib/paraview-2.4/libvtkImaging.so.pv2.4
(0xb6e96000)
        libutil.so.1 => /lib/libutil.so.1 (0xb6e92000)
        libvtkPVServerManager.so =>
/usr/lib/paraview-2.4/libvtkPVServerManager.so (0xb6c86000)
        libvtkPVServerCommonPython.so =>
/usr/lib/paraview-2.4/libvtkPVServerCommonPython.so (0xb6c84000)
        libvtkCommonPython.so => /usr/lib/paraview-2.4/libvtkCommonPython.so
(0xb6c6c000)
        libpython2.4.so.1.0 => /usr/lib/libpython2.4.so.1.0 (0xb6b77000)
        libvtkPVFiltersCS.so => /usr/lib/paraview-2.4/libvtkPVFiltersCS.so
(0xb6b33000)
        libvtkPVFilters.so => /usr/lib/paraview-2.4/libvtkPVFilters.so
(0xb69ca000)
        libvtkPVServerCommonCS.so =>
/usr/lib/paraview-2.4/libvtkPVServerCommonCS.so (0xb69b3000)
        libvtkPVServerCommon.so =>
/usr/lib/paraview-2.4/libvtkPVServerCommon.so (0xb6935000)
        libvtkXdmfCS.so => /usr/lib/paraview-2.4/libvtkXdmfCS.so (0xb692b000)
        libvtkXdmf.so => /usr/lib/paraview-2.4/libvtkXdmf.so (0xb68d8000)
        libXdmf.so => /usr/lib/paraview-2.4/libXdmf.so (0xb6888000)
        libvtkWidgetsCS.so => /usr/lib/paraview-2.4/libvtkWidgetsCS.so
(0xb686a000)
        libvtkWidgets.so.pv2.4 => /usr/lib/paraview-2.4/libvtkWidgets.so.pv2.4
(0xb67fc000)
        libhdf5.so.0 => /usr/lib/libhdf5.so.0 (0xb66d3000)
        libSPCTH.so => /usr/lib/paraview-2.4/libSPCTH.so (0xb66cc000)
        libvtkParallelCS.so => /usr/lib/paraview-2.4/libvtkParallelCS.so
(0xb669d000)
        libvtkParallel.so.pv2.4 =>
/usr/lib/paraview-2.4/libvtkParallel.so.pv2.4 (0xb6590000)
        libvtkHybridCS.so => /usr/lib/paraview-2.4/libvtkHybridCS.so
(0xb654b000)
        libvtkHybrid.so.pv2.4 => /usr/lib/paraview-2.4/libvtkHybrid.so.pv2.4
(0xb63ae000)
        libvtkexoIIc.so.pv2.4 => /usr/lib/paraview-2.4/libvtkexoIIc.so.pv2.4
(0xb6380000)
        libvtkNetCDF.so.pv2.4 => /usr/lib/paraview-2.4/libvtkNetCDF.so.pv2.4
(0xb6353000)
        libvtkVolumeRenderingCS.so =>
/usr/lib/paraview-2.4/libvtkVolumeRenderingCS.so (0xb632e000)
        libvtkVolumeRendering.so.pv2.4 =>
/usr/lib/paraview-2.4/libvtkVolumeRendering.so.pv2.4 (0xb5e03000)
        libvtkRenderingCS.so => /usr/lib/paraview-2.4/libvtkRenderingCS.so
(0xb5d73000)
        libvtkGenericFilteringCS.so =>
/usr/lib/paraview-2.4/libvtkGenericFilteringCS.so (0xb5d62000)
        libvtkGraphicsCS.so => /usr/lib/paraview-2.4/libvtkGraphicsCS.so
(0xb5c89000)
        libvtkImagingCS.so => /usr/lib/paraview-2.4/libvtkImagingCS.so
(0xb5c29000)
        libvtkIOCS.so => /usr/lib/paraview-2.4/libvtkIOCS.so (0xb5bbe000)
        libvtkFilteringCS.so => /usr/lib/paraview-2.4/libvtkFilteringCS.so
(0xb5af7000)
        libvtkCommonCS.so => /usr/lib/paraview-2.4/libvtkCommonCS.so
(0xb5a80000)
        libvtkClientServer.so => /usr/lib/paraview-2.4/libvtkClientServer.so
(0xb5a58000)
        libKWCommon.so => /usr/lib/paraview-2.4/libKWCommon.so (0xb5a3a000)
        libvtkGenericFiltering.so.pv2.4 =>
/usr/lib/paraview-2.4/libvtkGenericFiltering.so.pv2.4 (0xb5a02000)
        libvtkRendering.so.pv2.4 =>
/usr/lib/paraview-2.4/libvtkRendering.so.pv2.4 (0xb5786000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb5773000)
        libdl.so.2 => /lib/libdl.so.2 (0xb576f000)
        libvtkDICOMParser.so.pv2.4 =>
/usr/lib/paraview-2.4/libvtkDICOMParser.so.pv2.4 (0xb574e000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb5729000)
        libz.so.1 => /lib/libz.so.1 (0xb5718000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xb56fa000)
        libtiff.so.3 => /usr/lib/libtiff.so.3 (0xb56a6000)
        libexpat.so.0 => /usr/lib/libexpat.so.0 (0xb5686000)
        libavcodec.so.51 => /usr/lib/libavcodec.so.51 (0xb53a9000)
        libavformat.so.50 => /usr/lib/libavformat.so.50 (0xb5347000)
        libavutil.so.49 => /usr/lib/libavutil.so.49 (0xb5343000)
        libvtkMPEG2Encode.so.pv2.4 =>
/usr/lib/paraview-2.4/libvtkMPEG2Encode.so.pv2.4 (0xb532f000)
        libvtkftgl.so.pv2.4 => /usr/lib/paraview-2.4/libvtkftgl.so.pv2.4
(0xb5323000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb52b4000)
        libGL.so.1 => //usr//lib/opengl/nvidia/lib/libGL.so.1 (0xb522f000)
        libXt.so.6 => /usr/lib/libXt.so.6 (0xb51dd000)
        libSM.so.6 => /usr/lib/libSM.so.6 (0xb51d4000)
        libICE.so.6 => /usr/lib/libICE.so.6 (0xb51bc000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0xb50c9000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0xb50bb000)
        libvtksys.so.pv2.4 => /usr/lib/paraview-2.4/libvtksys.so.pv2.4
(0xb5095000)
        libstdc++.so.6 => /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libstdc++.so.6
(0xb4fcb000)
        libm.so.6 => /lib/libm.so.6 (0xb4fa9000)
        libgcc_s.so.1 => /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libgcc_s.so.1
(0xb4fa0000)
        libc.so.6 => /lib/libc.so.6 (0xb4e8a000)
        libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0xb4e4c000)
        libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0xb4d1d000)
        /lib/ld-linux.so.2 (0xb7f0b000)
        libmp3lame.so.0 => /usr/lib/libmp3lame.so.0 (0xb4c84000)
        libxvidcore.so.4 => /usr/lib/libxvidcore.so.4 (0xb4b6c000)
        libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0xb4b44000)
        libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0xb4a46000)
        libtheora.so.0 => /usr/lib/libtheora.so.0 (0xb4a17000)
        libfaad.so.0 => /usr/lib/libfaad.so.0 (0xb49db000)
        libfaac.so.0 => /usr/lib/libfaac.so.0 (0xb49ca000)
        libogg.so.0 => /usr/lib/libogg.so.0 (0xb49c5000)
        libGLcore.so.1 => //usr//lib/opengl/nvidia/lib/libGLcore.so.1
(0xb4202000)
        libnvidia-tls.so.1 => //usr//lib/opengl/nvidia/lib/libnvidia-tls.so.1
(0xb4200000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0xb41fd000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb41f7000)
        libmp4v2.so.0 => /usr/lib/libmp4v2.so.0 (0xb414c000)

No, the only thing left is to include ParaView in the KDE / Gnome menus and to
validate it for amd64.

I tried at home on amd64 and the compilation and demo went flawlessly, so I
don't think it is to take any major risk in marking the packet stable for x86
and amd64

Daniel 

(In reply to comment #33)
> It did the trick...
> 

Thanks for testing! The patch is in cvs now and I removed paraview
from package mask. I'll look into the kde/gnome menu thingy once
I've some spare time; it pretty much amounts to creating a 
paraview.desktop entry which shouldn't be too much work.

From now on, should there be any more bugs with paraview please open 
a new bug for it so we can keep track of issues separately.

Thanks again to everybody for the good work!

Best,
Markus