[Paraview] ParaView Web not compiling (UNCLASSIFIED)

Thu Aug 28 13:43:37 EDT 2014

Classification: UNCLASSIFIED
Caveats: NONE

Hi Seb,

Nope. I think we are good to disable ParaViewWeb from the compile for now.

By "building your own Python", do you mean doing the superbuild? I think I am 
doing the superbuild on lightning. I will try again 
with -DUSE_SYSTEM_python=OFF

Thanks
-simon

-----Original Message-----
From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
Sent: Thursday, August 28, 2014 1:32 PM
To: Su, Simon M CTR USARMY ARL (US)
Cc: Utkarsh Ayachit; Andy Bauer [andy.bauer at kitware.com]; 
paraview at paraview.org
Subject: Re: [Paraview] ParaView Web not compiling

Are you targeting ParaViewWeb server on your Cray? If not, you can safely 
disable it.

Otherwise, you may need to build your own Python along ParaView like we do in 
our ParaView binaries.

Seb

On Thu, Aug 28, 2014 at 11:18 AM, Su, Simon M CTR USARMY ARL (US) 
<simon.m.su.ctr at mail.mil> wrote:

	Sorry to have call qt out... I also think it is Python.. I have Python 2.6.6 
on my desktop and
	Python 2.6.9 on the new crays (lightning) at afrl that I am running the 
build.

	If Python 2.7 is a must, is there a work around? I doubt that they will 
update python on the crays just because I asked.... :)

	but garnet also has Python 2.6.9 and Andy was able to build ok? Andy?

	============================= error on crays with mesa build ==========

	[  5%] Compiling Python package 'web'
	Listing 
/home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web 
...
	Compiling 
/home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py 
...
	SyntaxError: ('invalid syntax', 
('/home/ssu/build/paraview-current/Build_2014-08-28_mesa/ParaViewSuperbuild_2014-08-28-build/paraview/src/paraview-build/lib/site-packages/vtk/web/testing.py', 
76, 47, 'TestModuleBrowsers = type("Enum", (), {k: i for i, k in 
enumerate(test_module_browsers)})\n'))

	gmake[5]: *** [VTK/Web/Python/web.build-complete] Error 1
	gmake[4]: *** [VTK/Web/Python/CMakeFiles/vtkWebPython.dir/all] Error 2
	gmake[4]: *** Waiting for unfinished jobs....

________________________________

	From: ParaView [paraview-bounces at paraview.org] on behalf of Sebastien 
Jourdain [sebastien.jourdain at kitware.com]
	Sent: Thursday, August 28, 2014 1:11 PM
	To: Utkarsh Ayachit
	Cc: paraview at paraview.org
	Subject: Re: [Paraview] ParaView Web not compiling

	Just out of curiosity, do you try to build ParaView with Python 2.6?

	If that's the case, that could make sense as ParaViewWeb require Python 2.7 
but I've only saw that error at run time.

	Seeing the error could certainly help.

	Seb

	On Thu, Aug 28, 2014 at 11:00 AM, Utkarsh Ayachit 
<utkarsh.ayachit at kitware.com> wrote:

		Andy,

		Can you elaborate on what the errors were? We should fix those.

		Utkarsh

		On Thu, Aug 28, 2014 at 12:57 PM, Andy Bauer <andy.bauer at kitware.com> wrote:
		> I was getting similar errors on a Cray machine. It seemed to be Python
		> related, if I remember correctly. When I turned off building ParaView Web 
it
		> went away. For me it was building without the Qt GUI. My CMake settings 
for
		> the build were:
		> =========
		> cmake -DCMAKE_C_COMPILER:FILEPATH=/
		> opt/gcc/4.8.2/bin/gcc \
		>     -DCMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.8.2/bin/g++ \
		>     -DBUILD_SHARED_LIBS:BOOL=OFF \
		>     -DBUILD_TESTING:BOOL=OFF \
		>     -DCMAKE_BUILD_TYPE:STRING=Release \
		>     -DOSMESA_INCLUDE_DIR:PATH=/
		> usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include \
		>
		> -DOSMESA_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libOSMesa.a
		> \
		>
		>     -DVISIT_BUILD_READER_GMV:BOOL=OFF \
		>     -DENABLE_MPI4PY:BOOL=ON \
		>     -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
		>     -DPARAVIEW_USE_MPI:BOOL=ON \
		>     -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
		>
		> -DBoost_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/tools/install/include
		> \
		>
		>     -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \
		>
		> -DMPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/include 
\
		>
		> -DMPI_C_LIBRARIES:STRING=/opt/cray/mpt/6.0.0/gni/mpich2-gnu/48/lib/libmpich_gnu_48.so
		> \
		>     -DOPENGL_gl_LIBRARY:FILEPATH= \
		>
		> -DOPENGL_glu_LIBRARY:FILEPATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/lib/libGLU.a
		> \
		>
		> -DOPENGL_INCLUDE_DIR:PATH=/usr/local/usp/DAAC/paraview/source/PV4.2/cross/install/include
		> \     -DPARAVIEW_ENABLE_WEB:BOOL=OFF \
		>     -DCMAKE_INSTALL_PREFIX:PATH=$INSTALLDIR \
		>     ../ParaView
		> ============
		>
		>
		>
		> On Thu, Aug 28, 2014 at 12:51 PM, Utkarsh Ayachit
		> <utkarsh.ayachit at kitware.com> wrote:
		>>
		>> Simon,
		>>
		>> What errors are you getting? It is definitely a temporary issue and
		>> will be fixed, however we're not seeing it on the dashboards so would
		>> help to see the errors. Qt version is certainly not the issue. 4.8.5
		>> is indeed supported Disabling Web will not affect catalyst. The
		>> ParaViewWeb+Catalyst demo also is a little independent since the
		>> catalyst part in that case doesn't really need the web components.
		>>
		>> Utkarsh
		>>
		>>
		>> On Thu, Aug 28, 2014 at 12:22 PM, Su, Simon M CTR USARMY ARL (US)
		>> <simon.m.su.ctr at mail.mil> wrote:
		>> > Hello,
		>> >
		>> > while compiling the latest ParaView for git (4.1.0-1560-gf37ec5f) - not
		>> > superbuild, I am not able to make it through all the way if I don't
		>> > disable
		>> > ParaView web using  -DPARAVIEW_ENABLE_WEB:BOOL=OFF on my cmake line.
		>> >
		>> > Is qt version (I am using qt version 4.8.5) an issue here? If so, what
		>> > is
		>> > the qt version that I should be using?  or this is just a temporary
		>> > state
		>> > that will eventually go away in the next PV release?
		>> >
		>> > If I turn off ParaView web, what feature will not be available? Will
		>> > catalyst be affected? I saw a demo once of catalyst via ParaView web.
		>> >
		>> > thanks
		>> > -simon
		>> >
		>> > _______________________________________________
		>> > Powered by www.kitware.com
		>> >
		>> > Visit other Kitware open-source projects at
		>> > http://www.kitware.com/opensource/opensource.html 
<http://www.kitware.com/opensource/opensource.html>
		>> >
		>> > Please keep messages on-topic and check the ParaView Wiki at:
		>> > http://paraview.org/Wiki/ParaView
		>> >
		>> > Follow this link to subscribe/unsubscribe:
		>> > http://public.kitware.com/mailman/listinfo/paraview 
<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
		>>
		>> Follow this link to subscribe/unsubscribe:
		>> http://public.kitware.com/mailman/listinfo/paraview 
<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 
<http://www.kitware.com/opensource/opensource.html>

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

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

Classification: UNCLASSIFIED
Caveats: NONE

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 9990 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140828/9e58b0ac/attachment-0001.bin>