[Paraview] Issues with OpenGL2 support for off-screen Mesa

[yvan . fournier]

Hello,

I recently encountered issues related to the OpenGL2 support for off-screen 
Mesa. Up to at least ParaView V5.1.2, I could use ParaView/Catalyst built with 
OSMesa with no specific issues (I mostly used OSMesa compiled without LLVM, as 
rendering did not represent a huge portion of my compute time.

I'm using Catalyst in the context of the Code_Saturne CFD code. By default, the 
code includes a plugin, linked to both ParaView or a Catalys edition (based on 
the info from the cmake entry in ParaView installs when 
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON is used). On Linux systems, the plugin 
is loaded with dlopen(, RTLD_LAZY).
We use Catalyst Python scripts, so the plugin goes through ParaView's Python 
layer also to render images.

On my personal PC, running Arch Linux I have not encountered any specific issue 
with recent ParaView changes and the move to OpenGL2 (actually, for on-screen 
redering, the Intel graphics driver/QT5 rendering issue leading to spurious 
transparencies that I had before seem to have disappeared, so things are 
actually better.

On company machines (workstations and clusters using EDF's Debian 8 flavor, 
with gcc version (Debian 4.9.2-10) 4.9.2, things are not working so well, as I 
get an error message related to missing OpenGL features starting with ParaView 
5.2 (and up to today's master).
I switched to Mesa 13.0.1, then 13.0.4, following the new instructions on the 
ParaView Wiki, but I still always get the following error:

"""
ERROR: In 
/home/D43345/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 
733
vtkOSOpenGLRenderWindow (0x808db80): GL version 2.1 with the gpu_shader4 
extension is not supported by your graphics driver but is required for the new 
OpenGL rendering backend. Please update your OpenGL driver. If you are using 
Mesa please make sure you have version 10.6.5 or later and make sure your 
driver in Mesa supports OpenGL 3.2.
GL_Version: 3.3 (Core Profile) Mesa 13.0.4.
"""

My mesa build used the following options (from the ParaView wiki) :

./configure --prefix=$HOME/opt/Mesa-13.0/arch/calibre9 --enable-opengl 
--disable-gles1 --disable-gles2 --disable-va --disable-xvmc --disable-vdpau 
--enable-shared-glapi --disable-texture-float --enable-gallium-llvm 
--enable-llvm-shared-libs --with-gallium-drivers=swrast,swr --disable-dri 
--with-dri-drivers= --disable-egl --with-egl-platforms= --disable-gbm 
--disable-glx --disable-osmesa --enable-gallium-osmesa 
--with-llvm-prefix=$HOME/opt/llvm-3.9/arch/calibre9

I tried both using the local llvm install (v3.5, which worked in part and could 
not compile OpenSwr), and a local build of LLVM 3.9.1 (shown above). I also 
added --enable-debug for my latest tests.

Things work slightly better with LLVM 3.9 than with 3.5, but I still get the 
above error mentioning the gpu_shader4 extension, whether exporting 
GALLIUM_DRIVER=llvmpipe or softpipe. With GALLIUM_DRIVER=swr, I have another 
error:

"""
Using OpenSWR :

SWR detected AVX2
SWR library load failure: 
/home/D43345/opt/Mesa-13.0/arch/calibre9/lib/libswrAVX2.so: undefined symbol: 
_glapi_Context
"""

During my testing, I also built a static version of my code, with a static 
build of ParaView (and the plugin replaced by a static link), but keeping the 
same dynamic library for OSMesa. And surprise, that version worked normally, 
producing the expected images (at least with the LLVM 3.9 build; with LLVM 3.5, 
I had the color map labels, but no colored slice...).

So the issue seems to be on the ParaView side more than on the OSMesa side. I 
have a debug build of the Code_Saturne/ParaView/OSMesa stack, but although I 
can explore where the final error occurs (in vtkOpenGLRenderWindow.cxx), and 
some GLES querying before that, I don't realy know where to look .

As the error occurs with a dynamic but not static build, is seems to be related 
to initialization issues, but I don't know VTK well enough to provide more 
precise info.

Has anybody encounted this issue ? Does anybody have suggestions ? I'm planning 
on trying other options than RTLD_LAZY on my plugin's side, but if that does 
not work, I'll be out of ideas.

Best regards,

  Yvan

PS: in case they are useful as a reference, the build options for Mesa used by 
Arch Linux (recently switched from 13 to 17), on the system on which I had zero 
issue, are the following:

  ./configure --prefix=/usr \
--sysconfdir=/etc \
--with-dri-driverdir=/usr/lib/xorg/modules/dri \
--with-gallium-drivers=r300,r600,radeonsi,nouveau,svga,swrast,virgl \
--with-dri-drivers=i915,i965,r200,radeon,nouveau,swrast \
--with-egl-platforms=x11,drm,wayland \
--with-vulkan-drivers=intel,radeon \
--disable-xvmc \
--enable-gallium-llvm \
--enable-llvm-shared-libs \
--enable-shared-glapi \
--enable-libglvnd \
--enable-egl \
--enable-glx \
--enable-glx-tls \
--enable-gles1 \
--enable-gles2 \
--enable-gbm \
--enable-dri \
--enable-osmesa \

Re: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641

[Nabil Ghodbane]

Hi
Thanks for the reply. Did someone else manage to get this approach based on
the superbuilder machinery on a Centos 7 node? As I wrote it previously the
installation works nicely on Ubuntu but fails on CentOS.
I will appréciateur any feedback about it.
Thanks

On Tuesday, February 21, 2017, Ben Boeckel  wrote:

> On Tue, Feb 21, 2017 at 18:48:37 +0100, Nabil Ghodbane wrote:
> > fine, I started a parallel build on another node using Python 2.7.12, it
> > seems to be compiling so far...
> > As I wrote it previously, the first compilation based on Python 2.7.11
> > shipped by the superbuilder fails  with the following message:
> > do you know by chance whether I do have to switch on/off some flag ?
>
> Hmm. This looks like a problem with ParaView itself. What HDF5 settings
> are you using in the superbuild and what HDF5-related settings are set
> in `superbuild/paraview/build/CMakeCache.txt`.
>
> --Ben
>


-- 
Nabil Ghodbane (PhD. Habil.)
Mailto: nabil.ghodb...@gmail.com
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [EXTERNAL] Re: [Non-DoD Source] Re: Superbuild repo change?

[Scott, W Alan]

I am not sure of this, but I believe I also saw this (i.e., git pull and git 
submodule update not updating Superbuild) a week ago.  Will pay more attention.

Alan

> -Original Message-
> From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Cory
> Quammen
> Sent: Wednesday, February 22, 2017 7:05 AM
> To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
> 
> Cc: ParaView 
> Subject: [EXTERNAL] Re: [Paraview] [Non-DoD Source] Re: Superbuild repo
> change?
> 
> Rick,
> 
> Interesting. I would think that should have worked, assuming you are on the
> 'master' branch, and my local testing suggests it would.
> 
> What I usually do these days to be be more explicit in my git updates is:
> 
> git checkout master
> git fetch origin
> git merge origin/master
> 
> 'git pull' does essentially the last two if you are on the 'master'
> branch. If you are on another branch, FETCH_HEAD may already point to the
> tip of the remote branch, and so there may be nothing to merge.
> 
> In any case, a fresh 'git clone' is sure to work, though as you say, you 
> really
> shouldn't have to.
> 
> Thanks for testing the release candidate.
> 
> Best,
> Cory
> 
> On Wed, Feb 22, 2017 at 8:10 AM, Angelini, Richard C (Rick) CIV USARMY
> RDECOM ARL (US)  wrote:
> > Cory - so I did a “git pull” and “git submodule update” in my existing
> > paraview-superbuild repository directory and that 5.3.0-RC1 information
> > was not in the versions.cmake file. I did a clean “git clone” and I
> > then received the correct files.I’m not a git expert - so I’m not
> > sure why I had to do a clean “git clone”.   I thought I “git pull” should
> > have done a proper update.  I must be missing something with my
> > repository update commands …..
> >
> > ___
> > Rick Angelini
> > USArmy Research Laboratory
> > CISD/HPC Architectures Team
> > Phone:  410-278-6266
> >
> >
> >
> >
> > -Original Message-
> > From: Cory Quammen 
> > Date: Tuesday, February 21, 2017 at 1:36 PM
> > To: Rick Angelini 
> > Cc: "ben.boec...@kitware.com" , ParaView
> > 
> > Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
> >
> > Rick,
> >
> > What is the SHA-1 for last commit in your paraview-superbuild
> > directory? The latest commit on master is
> > 22e4b36087b523e01994b90f7b1c5eabb6c0755b. In the file versions.cmake
> > at line 63, 5.3.0-RC1 should be listed as a version option.
> >
> > Thanks,
> > Cory
> >
> > On Tue, Feb 21, 2017 at 11:31 AM, Angelini, Richard C (Rick) CIV
> > USARMY RDECOM ARL (US)  wrote:
> >> I did a “git pull” and “git submodule update” in the paraview-superbuild
> >> directory.   I then changed the source flag in my cmake command:
> >>
> >> -Dparaview_SOURCE_SELECTION="5.3.0-RC1”
> >>
> >> and I get this error when doing a clean build.
> >>
> >> -- Detecting CXX compile features - done
> >> -- Check size of void*
> >> -- Check size of void* - done
> >> CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:338
> >> (message):
> >>   The 5.3.0-RC1 source selection for paraview does not exist.
> >> Call Stack (most recent call first):
> >>   versions.cmake:62 (superbuild_set_selectable_source)
> >>   superbuild/CMakeLists.txt:96 (include)
> >>
> >>
> >> I grepp’ed through the paraview-superbuild directory and I don’t see
> >> any references to 5.3.
> >>
> >>
> >>
> >>
> >> 
> >> Rick Angelini
> >> USArmy Research Laboratory
> >> CISD/HPC Architectures Team
> >> Phone:  410-278-6266
> >>
> >>
> >>
> >>
> >> -Original Message-
> >> From: Cory Quammen 
> >> Date: Tuesday, February 21, 2017 at 10:07 AM
> >> To: Rick Angelini 
> >> Cc: "ben.boec...@kitware.com" , ParaView
> >> 
> >> Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
> >>
> >> All active links contained in this email were disabled.  Please
> >>verify the  identity of the sender, and confirm the authenticity of
> >>all links  contained within the message prior to copying and pasting
> >>the address to a  Web browser.
> >>
> >>
> >>
> >>
> >> 
> >>
> >> Hi Rick,
> >>
> >> From paraview-superbuild master (remember to run 'git submodule
> >> update' after updating master), you should be able to set
> >> paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and
> build.
> >>
> >> These directions are distilled from the README.md file in the
> >> superbuild directory [1]. Relevant excerpt:
> >>
> >> "3. Another option is to use a source tarball of a ParaView release.
> >> For that, set paraview_SOURCE_SELECTION to the version to build such
> >> as 5.2.0. The superbuild offers the lastest stable release 

Re: [Paraview] Paraview closes with a core dump

[Mathieu Westphal]

Hi

Well, you found it yourself, looks like you have some problem with OpenGL
and x windows.
Can't help you much more here, let me know when you are able to fix it if
paraview still crashes.
Also, if glxinfo does not work, i would expect all x application to crash
as well.

Regards,

Mathieu Westphal

On Wed, Feb 22, 2017 at 6:26 PM, Robert Sawko  wrote:

>
> Thanks for looking into it, Mathieu.
>
> >- Is your system up to date ?
> It's quite up to date. See below.
> $ uname -a
> Linux avignon 4.9.9-1-ARCH #1 SMP PREEMPT Thu Feb 9 19:07:09 CET 2017
> x86_64 GNU/Linux
>
> >- Are you running X ? Wayland ?
> Yes, for X. Never heard of Wayland.
>
> >- What DE/WM are you running ?
> No DE, but Xmonad as WM.
>
> >- What graphic card do you have ? With which drivers version ?
> Nvidia Quadro. I've got nvidia driver version 378.13-1. There's a slightly
> newer one in the repo.
>
> >- What version of opengl is installed ? please provide glxinfo output.
>
> $ glxinfo
> name of display: :0.0
> Error: couldn't find RGB GLX visual or fbconfig
>
> Oops... that looks like a problem. I could try downgrading opengl.
>
> >- There should be some error message before the segfault, but we can't
> >see any, did you removed them or are they missing ?
>
> I haven't removed anything from the gdb output. Running paraview from bash
> is
> core-dumps silently.
>
> >- Can you check in your source that
> >paraview/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:485
> contains
>
> Yes, these lines are there.
>
> Robert
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Paraview closes with a core dump

[Robert Sawko]

Thanks for looking into it, Mathieu.

>- Is your system up to date ?
It's quite up to date. See below.
$ uname -a
Linux avignon 4.9.9-1-ARCH #1 SMP PREEMPT Thu Feb 9 19:07:09 CET 2017 x86_64 
GNU/Linux

>- Are you running X ? Wayland ?
Yes, for X. Never heard of Wayland.

>- What DE/WM are you running ?
No DE, but Xmonad as WM.

>- What graphic card do you have ? With which drivers version ?
Nvidia Quadro. I've got nvidia driver version 378.13-1. There's a slightly
newer one in the repo.

>- What version of opengl is installed ? please provide glxinfo output.

$ glxinfo 
name of display: :0.0
Error: couldn't find RGB GLX visual or fbconfig

Oops... that looks like a problem. I could try downgrading opengl.

>- There should be some error message before the segfault, but we can't
>see any, did you removed them or are they missing ?

I haven't removed anything from the gdb output. Running paraview from bash is
core-dumps silently.

>- Can you check in your source that
>paraview/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:485 contains

Yes, these lines are there.

Robert
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Paraview closes with a core dump

[Mathieu Westphal]

Looks like a Xorg problem.

Please specify :
- Is your system up to date ?
- Are you running X ? Wayland ?
- What DE/WM are you running ?
- What graphic card do you have ? With which drivers version ?
- What version of opengl is installed ? please provide glxinfo output.
- There should be some error message before the segfault, but we can't see
any, did you removed them or are they missing ?
- Can you check in your source that
paraview/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx:485 contains :

   6   if (!this->WindowId)
   5   {
   4 v = this->GetDesiredVisualInfo();
   3 if (!v)
   2 {
   1   vtkErrorMacro(<< "Could not find a decent visual\n");
485abort();
   1 }

Regards

Mathieu Westphal

On Wed, Feb 22, 2017 at 6:01 PM, Robert Sawko  wrote:

> Thanks. Here's the gdb output. I did compile in Debug mode.
>
> Robert
> --
> Noah's Ark for plants:
> http://en.wikipedia.org/wiki/Svalbard_Global_Seed_Vault
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Paraview closes with a core dump

[Mathieu Westphal]

Hi

Please make sure ParaView is compiled in Debug, run it with gdb, then
forward the backtrace.

Mathieu Westphal

On Wed, Feb 22, 2017 at 5:49 PM, Robert Sawko  wrote:

> Unfortunately even a minimal compilation of ParaView (no options). I am
> attaching the stack trace. Let me know if you have any ideas.
>
> Robert
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Duplicate Renderview

[Adam Dershowitz]

I have a pipeline setup, with a good renderview.  I want to then make a split 
view, that is identical, except for the camera angle.  When I try to split my 
view, or create a new view,  they show up empty.  I can then start manually 
turning on, and coloring everything how I want it.  But, it seems like there 
should be an option to “duplicate current pipeline settings” as a starting 
point.  Then, I could move the camera or make any other changes that I want 
from there.
I did search around in Paraview and on the web, but didn’t find anything.  Is 
there an easy way to do this?  I did find a few other discussions about this, 
with suggested scripts, but those fail for me as well.
I’m using Paraview 5.2, although I also looked around briefly for a way to do 
this in 5.3RC1.

Thanks,

-- Adam

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] problems with packaging of superbuild

[Cory Quammen]

Stefan,

Are you building from the v5.2.0 tag in paraview-superbuild? If so, I
recommend building from current master instead. ParaView 5.2.0 is
still the default version in master, but there have been some fixes in
the superbuild that may address the problems you have run into since
v5.2.0 was tagged in the superbuild.

HTH,
Cory

On Wed, Feb 22, 2017 at 8:04 AM, Stefan Vater  wrote:
> Once again...
>
> so the old two problems seem to still exist. I made some changes in the camke
> files to circumvent them, but forgot that they are still there.
>
> Stefan
>
> Am Mittwoch, 22. Februar 2017, 12:33:53 CET schrieb Stefan Vater:
>> Hi,
>>
>> it seems that these errors resulted from the fact, that I set an absolute
>> install path. However, now I have the problem that the packaging fails to
>> find cpack/paraview/TGZ/build/install.manifest, which is nonexistent. At
>> least this is my guess. The error message is:
>>
>> [...]
>> 1: CPack: Install projects
>> 1: CPack: - Run preinstall target for: cpack-paraview
>> 1: CPack: - Install project: cpack-paraview
>> 1: CPack Verbose: Install configuration: "Release"
>> 1: CMake Error at
>> /home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build/cmake_install.cmake:
>> 45 (message): 1:   Failed to install pvdataserver:
>> 1:
>> 1:   Traceback (most recent call last):
>> 1:
>> 1: File
>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
>> nix.py", line 504, in  1:   main(sys.argv[1:])
>> 1: File
>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
>> nix.py", line 496, in main 1:   _install_binary(main_exe, is_excluded,
>> bundle_dest, opts.libdir, installed, manifest, dry_run=opts.dry_run) 1:
>> File
>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
>> nix.py", line 400, in _install_binary 1:   deps =
>> binary.dependencies.values()
>> 1: File
>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
>> nix.py", line 197, in dependencies 1:   deplib =
>> Library.create_from_reference(dep, self)
>> 1: File
>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
>> nix.py", line 258, in create_from_reference 1:
>> paths.extend(cls.default_search_paths())
>> 1: File
>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
>> nix.py", line 230, in default_search_paths 1:   cls.__search_cache =
>> pipe().split('\n')
>> 1: File
>> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
>> nix.py", line 22, in __call__ 1:   command =
>> subprocess.Popen(command_args, stdin=last_input, stdout=subprocess.PIPE) 1:
>> File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ 1:
>> errread, errwrite)
>> 1: File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child
>> 1:   raise child_exception
>> 1:
>> 1:   OSError: [Errno 2] No such file or directory
>> 1:
>> 1:
>> 1:
>> 1: CPack Error: Error when generating package: ParaView
>> 1: CMake Error at
>> /home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cm
>> ake:21 (message): 1:   CPack failed with exit code 1
>> 1:
>> 1:
>> 1/1 Test #1: cpack-paraview-TGZ ...***Failed0.10 sec
>>
>> Any suggestions?
>>
>> Stefan
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
> --
> Stefan Vater
> Research group "Numerical Methods in Geosciences"
> CEN - Center for Earth System Research and Sustainability
> Universität Hamburg
> Grindelberg 5, D-20144 Hamburg, Germany
> Phone: +49 - 40 - 42838 7746
> Fax:   +49 - 40 - 42838 7712
> Email: stefan.va...@uni-hamburg.de
> URL: http://www.clisap.de/vater
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview



-- 
Cory Quammen
Staff R Engineer
Kitware, Inc.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this 

Re: [Paraview] Compiling Paraview 5.2 GCC 4.8 vtkOpenGLRenderWindow.cxx, line 641

[Ben Boeckel]

On Wed, Feb 22, 2017 at 09:37:47 +0100, Nabil Ghodbane wrote:
> - I am requesting USE_SYSTEM_hdf5 = OFF
> but looking as you suggested in superbuild/paraview/build/CMakeCache.txt, I
> can see that VTK_USE_SYSTEM_HDF5:BOOL=TRUE
> Shouldn't this be FALSE ?

>From ParaView's point of view, it is using a "system" HDF5, but it is
being provided by the superbuild itself. It looks like it is finding the
superbuild's HDF5, so something else is going wrong here :( .

> Find attached, the CMakeCache.txt, How can I workaround this issue?

It will need investigation. I'll try and get to it this week.

> Find below some additional informations:
> -  it works on Ubuntu (I tried my own Python), but I need to stick to an
> older glibc :(
> - on a Debian node, it fails if I use my local Python installation, while
> trying to compile numpy: "/usr/lib/python2.7/distutils/sysconfig.py"

More information is needed to help with this.

--Ben
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

[Ben Boeckel]

On Wed, Feb 22, 2017 at 13:10:04 +, Angelini, Richard C (Rick) CIV USARMY 
RDECOM ARL (US) wrote:
> Cory - so I did a “git pull” and “git submodule update” in my existing
> paraview-superbuild repository directory and that 5.3.0-RC1 information
> was not in the versions.cmake file. I did a clean “git clone” and I
> then received the correct files.I’m not a git expert - so I’m not
> sure why I had to do a clean “git clone”.   I thought I “git pull” should
> have done a proper update.  I must be missing something with my
> repository update commands …..

What is the output of the following commands:

  - git config branch.master.remote
  - git remote show $output_from_previous_command
  - git remote show origin

--Ben
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

[Cory Quammen]

Rick,

Interesting. I would think that should have worked, assuming you are
on the 'master' branch, and my local testing suggests it would.

What I usually do these days to be be more explicit in my git updates is:

git checkout master
git fetch origin
git merge origin/master

'git pull' does essentially the last two if you are on the 'master'
branch. If you are on another branch, FETCH_HEAD may already point to
the tip of the remote branch, and so there may be nothing to merge.

In any case, a fresh 'git clone' is sure to work, though as you say,
you really shouldn't have to.

Thanks for testing the release candidate.

Best,
Cory

On Wed, Feb 22, 2017 at 8:10 AM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US)  wrote:
> Cory - so I did a “git pull” and “git submodule update” in my existing
> paraview-superbuild repository directory and that 5.3.0-RC1 information
> was not in the versions.cmake file. I did a clean “git clone” and I
> then received the correct files.I’m not a git expert - so I’m not
> sure why I had to do a clean “git clone”.   I thought I “git pull” should
> have done a proper update.  I must be missing something with my
> repository update commands …..
>
> ___
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Cory Quammen 
> Date: Tuesday, February 21, 2017 at 1:36 PM
> To: Rick Angelini 
> Cc: "ben.boec...@kitware.com" , ParaView
> 
> Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
>
> Rick,
>
> What is the SHA-1 for last commit in your paraview-superbuild
> directory? The latest commit on master is
> 22e4b36087b523e01994b90f7b1c5eabb6c0755b. In the file versions.cmake
> at line 63, 5.3.0-RC1 should be listed as a version option.
>
> Thanks,
> Cory
>
> On Tue, Feb 21, 2017 at 11:31 AM, Angelini, Richard C (Rick) CIV
> USARMY RDECOM ARL (US)  wrote:
>> I did a “git pull” and “git submodule update” in the paraview-superbuild
>> directory.   I then changed the source flag in my cmake command:
>>
>> -Dparaview_SOURCE_SELECTION="5.3.0-RC1”
>>
>> and I get this error when doing a clean build.
>>
>> -- Detecting CXX compile features - done
>> -- Check size of void*
>> -- Check size of void* - done
>> CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:338
>> (message):
>>   The 5.3.0-RC1 source selection for paraview does not exist.
>> Call Stack (most recent call first):
>>   versions.cmake:62 (superbuild_set_selectable_source)
>>   superbuild/CMakeLists.txt:96 (include)
>>
>>
>> I grepp’ed through the paraview-superbuild directory and I don’t see any
>> references to 5.3.
>>
>>
>>
>>
>> 
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -Original Message-
>> From: Cory Quammen 
>> Date: Tuesday, February 21, 2017 at 10:07 AM
>> To: Rick Angelini 
>> Cc: "ben.boec...@kitware.com" , ParaView
>> 
>> Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
>>
>> All active links contained in this email were disabled.  Please verify
>>the
>> identity of the sender, and confirm the authenticity of all links
>> contained within the message prior to copying and pasting the address to
>>a
>> Web browser.
>>
>>
>>
>>
>> 
>>
>> Hi Rick,
>>
>> From paraview-superbuild master (remember to run 'git submodule
>> update' after updating master), you should be able to set
>> paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and build.
>>
>> These directions are distilled from the README.md file in the
>> superbuild directory [1]. Relevant excerpt:
>>
>> "3. Another option is to use a source tarball of a ParaView release.
>> For that, set paraview_SOURCE_SELECTION to the version to build such
>> as 5.2.0. The superbuild offers the lastest stable release as well as
>> release candidate in preparation for the release. This is the best way
>> to build a released version of ParaView."
>>
>> For each release candidate and release, we add an entry under
>> paraview_SOURCE_SELECTION that you can select.
>>
>> Let us know if you run into problems.
>>
>> Thanks,
>> Cory
>>
>> [1]
>>
>>Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/maste
>>r
>> /README.md
>>
>> On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY
>> RDECOM ARL (US)  wrote:
>>> What are the instructions for using PVSB to build the 5.3- RC ?
>>> 
>>> Rick Angelini
>>> USArmy Research Laboratory
>>> CISD/HPC Architectures Team
>>> Phone:  410-278-6266
>>>
>>>
>>>
>>>
>>> 

Re: [Paraview] ParaView v5.2.0: Problems with inspecting Use Below (Above) Range Color

[Nenad Vujicic]

Utkarsh,

Thank you very much! I made mistake by casting vtkScalarsToColors to
vtkLookupTable always, without inspecting of other branches! When I put
conditional checking if it is maybe
vtkPVDiscretizableColorTransferFunction, it started working! Thank you very
much for your help!

Nenad.

On Wed, Feb 22, 2017 at 2:12 AM, Utkarsh Ayachit <
utkarsh.ayac...@kitware.com> wrote:

> Where are you getting the vtkLookupTable from? ParaView doesn't use
> vtkLookupTable directly, is uses vtkPVDiscretizableColorTransferFunction
> 
>  .
>
> Utkarsh
>
> On Tue, Feb 21, 2017 at 11:42 AM, Nenad Vujicic  wrote:
>
>> Hello everyone,
>>
>> I'm trying to inspect values of "UseBelowRangeColor" and
>> "UseAboveRangeColor" flags from my ParaView exporter plugin by:
>>
>> 1. Retrieving vtkCompositePolyDataMapper2 from currently active view and
>> rendering window, then,
>> 2. Getting it's vtkLookupTable and then calling GetUseAboveRangeColor()
>> and GetUseBelowRangeColor(),
>>
>> However, first call (for checking using above range color) always passes
>> and returns some big number and second one (for checking using below range
>> color) always crashes, regardless whether flags are turned ON / OFF in
>> ParaView UI.
>>
>> Any suggestions about this or ideas how I could pick up these values in
>> different way?
>>
>> Thanks in advance!
>> Nenad.
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Paraview closes with a core dump

[Mathieu Westphal]

You are right, i did not check the core dump.
Let me know how it goes.

Mathieu Westphal

On Wed, Feb 22, 2017 at 2:36 PM, Robert Sawko  wrote:

> I was convinced I attached stack trace too. Please see core.dump file. It
> may
> be a red herring but there are several references to libQt5Core there. I am
> rebuilding with Qt5 now, but will also try a more minimal build with Qt4
> later.
>
> Thanks for quick reply.
> Robert
> --
> Tropics in Cornwall:
> http://en.wikipedia.org/wiki/Eden_Project
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Paraview closes with a core dump

[Robert Sawko]

I was convinced I attached stack trace too. Please see core.dump file. It may
be a red herring but there are several references to libQt5Core there. I am
rebuilding with Qt5 now, but will also try a more minimal build with Qt4 later.

Thanks for quick reply.
Robert
-- 
Tropics in Cornwall:
http://en.wikipedia.org/wiki/Eden_Project
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Paraview closes with a core dump

[Mathieu Westphal]

Hi

ArchLinux user here.
Your CMakeCache.txt looks like a QT4 configuration, no occurence of libQt5.
I can build with Qt4 without any problem.

You may want to :
 - CleanUp your build directory and configure and build again. Unless
specific needs, i suggest you only set PARAVIEW_QT_VERSION to 4 and build
 - If it stills segfault, run with gdb and report the backtrace
 - Try with qt5 as well.

Regards


Mathieu Westphal

On Wed, Feb 22, 2017 at 2:12 PM, Robert Sawko  wrote:

> Hi,
>
> This is Arch Linux user again. Parview no longer opens for me. It just ends
> with a core dump (attached). It seems it's something to do with Arch Linux
> forward looking policy of favouring QT5. I have specified in the
> compilation
> to build with QT4 (see attached CMakeCache.txt), but on run it still picks
> libQt5Core.so.
>
> I will now try to rebuild with QT5 but there was a perspective issue with
> that
> before.
>
> Does anyone have any suggestions, please?
>
> Thanks,
> Robert
> --
> Tropics in Cornwall:
> http://en.wikipedia.org/wiki/Eden_Project
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

[Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)]

Cory - so I did a “git pull” and “git submodule update” in my existing
paraview-superbuild repository directory and that 5.3.0-RC1 information
was not in the versions.cmake file. I did a clean “git clone” and I
then received the correct files.I’m not a git expert - so I’m not
sure why I had to do a clean “git clone”.   I thought I “git pull” should
have done a proper update.  I must be missing something with my
repository update commands …..

___
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-Original Message-
From: Cory Quammen 
Date: Tuesday, February 21, 2017 at 1:36 PM
To: Rick Angelini 
Cc: "ben.boec...@kitware.com" , ParaView

Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

Rick,

What is the SHA-1 for last commit in your paraview-superbuild
directory? The latest commit on master is
22e4b36087b523e01994b90f7b1c5eabb6c0755b. In the file versions.cmake
at line 63, 5.3.0-RC1 should be listed as a version option.

Thanks,
Cory

On Tue, Feb 21, 2017 at 11:31 AM, Angelini, Richard C (Rick) CIV
USARMY RDECOM ARL (US)  wrote:
> I did a “git pull” and “git submodule update” in the paraview-superbuild
> directory.   I then changed the source flag in my cmake command:
>
> -Dparaview_SOURCE_SELECTION="5.3.0-RC1”
>
> and I get this error when doing a clean build.
>
> -- Detecting CXX compile features - done
> -- Check size of void*
> -- Check size of void* - done
> CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:338
> (message):
>   The 5.3.0-RC1 source selection for paraview does not exist.
> Call Stack (most recent call first):
>   versions.cmake:62 (superbuild_set_selectable_source)
>   superbuild/CMakeLists.txt:96 (include)
>
>
> I grepp’ed through the paraview-superbuild directory and I don’t see any
> references to 5.3.
>
>
>
>
> 
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -Original Message-
> From: Cory Quammen 
> Date: Tuesday, February 21, 2017 at 10:07 AM
> To: Rick Angelini 
> Cc: "ben.boec...@kitware.com" , ParaView
> 
> Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
>
> All active links contained in this email were disabled.  Please verify
>the
> identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to
>a
> Web browser.
>
>
>
>
> 
>
> Hi Rick,
>
> From paraview-superbuild master (remember to run 'git submodule
> update' after updating master), you should be able to set
> paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and build.
>
> These directions are distilled from the README.md file in the
> superbuild directory [1]. Relevant excerpt:
>
> "3. Another option is to use a source tarball of a ParaView release.
> For that, set paraview_SOURCE_SELECTION to the version to build such
> as 5.2.0. The superbuild offers the lastest stable release as well as
> release candidate in preparation for the release. This is the best way
> to build a released version of ParaView."
>
> For each release candidate and release, we add an entry under
> paraview_SOURCE_SELECTION that you can select.
>
> Let us know if you run into problems.
>
> Thanks,
> Cory
>
> [1]
> 
>Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/maste
>r
> /README.md
>
> On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY
> RDECOM ARL (US)  wrote:
>> What are the instructions for using PVSB to build the 5.3- RC ?
>> 
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -Original Message-
>> From: Ben Boeckel 
>> Reply-To: "ben.boec...@kitware.com" 
>> Date: Wednesday, February 15, 2017 at 11:34 AM
>> To: Rick Angelini 
>> Cc: ParaView 
>> Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change?
>>
>> On Wed, Feb 15, 2017 at 13:50:13 +, Angelini, Richard C (Rick) CIV
>> USARMY RDECOM ARL (US) wrote:
>>> I did a fresh pull of the ParaView superbuild repository, and now I
>>>can’t do
>>> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5).
>>>
>>> First, I had to remove the entries for “qt” and “scipy" in the
>>> CMakeLists.txt:
>>
>> You need to run `git submodule update` to update the common-superbuild
>> bits.
>>
>>> After removing those entries, the cmake completes and the build starts
>>>and
>>> passes out in qt4.
>>> I’m not sure why it’s complaining about OS 

[Paraview] Paraview closes with a core dump

[Robert Sawko]

Hi,

This is Arch Linux user again. Parview no longer opens for me. It just ends
with a core dump (attached). It seems it's something to do with Arch Linux
forward looking policy of favouring QT5. I have specified in the compilation
to build with QT4 (see attached CMakeCache.txt), but on run it still picks
libQt5Core.so.

I will now try to rebuild with QT5 but there was a perspective issue with that
before.

Does anyone have any suggestions, please?

Thanks,
Robert
-- 
Tropics in Cornwall:
http://en.wikipedia.org/wiki/Eden_Project


paraview_core_dump.tar.gz
Description: Binary data
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] problems with packaging of superbuild

[Stefan Vater]

Once again...

so the old two problems seem to still exist. I made some changes in the camke 
files to circumvent them, but forgot that they are still there.

Stefan

Am Mittwoch, 22. Februar 2017, 12:33:53 CET schrieb Stefan Vater:
> Hi,
> 
> it seems that these errors resulted from the fact, that I set an absolute
> install path. However, now I have the problem that the packaging fails to
> find cpack/paraview/TGZ/build/install.manifest, which is nonexistent. At
> least this is my guess. The error message is:
> 
> [...]
> 1: CPack: Install projects
> 1: CPack: - Run preinstall target for: cpack-paraview
> 1: CPack: - Install project: cpack-paraview
> 1: CPack Verbose: Install configuration: "Release"
> 1: CMake Error at
> /home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build/cmake_install.cmake:
> 45 (message): 1:   Failed to install pvdataserver:
> 1:
> 1:   Traceback (most recent call last):
> 1:
> 1: File
> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
> nix.py", line 504, in  1:   main(sys.argv[1:])
> 1: File
> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
> nix.py", line 496, in main 1:   _install_binary(main_exe, is_excluded,
> bundle_dest, opts.libdir, installed, manifest, dry_run=opts.dry_run) 1:
> File
> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
> nix.py", line 400, in _install_binary 1:   deps =
> binary.dependencies.values()
> 1: File
> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
> nix.py", line 197, in dependencies 1:   deplib =
> Library.create_from_reference(dep, self)
> 1: File
> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
> nix.py", line 258, in create_from_reference 1:  
> paths.extend(cls.default_search_paths())
> 1: File
> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
> nix.py", line 230, in default_search_paths 1:   cls.__search_cache =
> pipe().split('\n')
> 1: File
> "/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.u
> nix.py", line 22, in __call__ 1:   command =
> subprocess.Popen(command_args, stdin=last_input, stdout=subprocess.PIPE) 1:
> File "/usr/lib/python2.7/subprocess.py", line 679, in __init__ 1:  
> errread, errwrite)
> 1: File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child
> 1:   raise child_exception
> 1:
> 1:   OSError: [Errno 2] No such file or directory
> 1:
> 1:
> 1:
> 1: CPack Error: Error when generating package: ParaView
> 1: CMake Error at
> /home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cm
> ake:21 (message): 1:   CPack failed with exit code 1
> 1:
> 1:
> 1/1 Test #1: cpack-paraview-TGZ ...***Failed0.10 sec
> 
> Any suggestions?
> 
> Stefan
> 
> ___
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
-- 
Stefan Vater
Research group "Numerical Methods in Geosciences"
CEN - Center for Earth System Research and Sustainability
Universität Hamburg
Grindelberg 5, D-20144 Hamburg, Germany
Phone: +49 - 40 - 42838 7746
Fax:   +49 - 40 - 42838 7712
Email: stefan.va...@uni-hamburg.de
URL: http://www.clisap.de/vater
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] problems with packaging of superbuild

[Stefan Vater]

Hi,

it seems that these errors resulted from the fact, that I set an absolute 
install 
path. However, now I have the problem that the packaging fails to find 
cpack/paraview/TGZ/build/install.manifest, which is nonexistent. At least this 
is my guess. The error message is:

[...]
1: CPack: Install projects
1: CPack: - Run preinstall target for: cpack-paraview
1: CPack: - Install project: cpack-paraview
1: CPack Verbose: Install configuration: "Release"
1: CMake Error at 
/home/paraview/paraview-5.2.0/cpack/paraview/TGZ/build/cmake_install.cmake:45 
(message):
1:   Failed to install pvdataserver:
1: 
1:   Traceback (most recent call last):
1: 
1: File 
"/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py",
 line 504, in 
1:   main(sys.argv[1:])
1: File 
"/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py",
 line 496, in main
1:   _install_binary(main_exe, is_excluded, bundle_dest, opts.libdir, 
installed, manifest, dry_run=opts.dry_run)
1: File 
"/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py",
 line 400, in _install_binary
1:   deps = binary.dependencies.values()
1: File 
"/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py",
 line 197, in dependencies
1:   deplib = Library.create_from_reference(dep, self)
1: File 
"/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py",
 line 258, in create_from_reference
1:   paths.extend(cls.default_search_paths())
1: File 
"/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py",
 line 230, in default_search_paths
1:   cls.__search_cache = pipe().split('\n')
1: File 
"/home/paraview/paraview-superbuild/superbuild/cmake/scripts/fixup_bundle.unix.py",
 line 22, in __call__
1:   command = subprocess.Popen(command_args, stdin=last_input, 
stdout=subprocess.PIPE)
1: File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
1:   errread, errwrite)
1: File "/usr/lib/python2.7/subprocess.py", line 1259, in _execute_child
1:   raise child_exception
1: 
1:   OSError: [Errno 2] No such file or directory
1: 
1: 
1: 
1: CPack Error: Error when generating package: ParaView
1: CMake Error at 
/home/paraview/paraview-superbuild/superbuild/cmake/scripts/package_test.cmake:21
 (message):
1:   CPack failed with exit code 1
1: 
1: 
1/1 Test #1: cpack-paraview-TGZ ...***Failed0.10 sec

Any suggestions?

Stefan

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview