[Paraview] gpu_shader4 extension is not supported
Chuck Atkins
chuck.atkins at kitware.com
Fri May 12 10:46:11 EDT 2017
Hi Patrick,
When you build Mesa, what does the summary at the end of ./configure look
like? That should let us know if Mesa is getting built with sufficient
options. For example, when I configure with LLVM 4.0 and Mesa 17.0.5 using
the settings described on the ParaView Wiki,
http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D#Installing_Mesa_llvmpipe_and_swr_drivers,
I get the following summary from configure:
prefix: /opt/mesa/17.0.5
exec_prefix: ${prefix}
libdir: ${exec_prefix}/lib
includedir: ${prefix}/include
OpenGL: yes (ES1: no ES2: no)
OSMesa: libOSMesa (Gallium)
GLX: no
EGL: no
GBM: no
Vulkan drivers: no
llvm: yes
llvm-config: /opt/clang/4.0.0/bin/llvm-config
llvm-version: 4.0.0
Gallium drivers: swrast swr
Gallium st: mesa
HUD extra stats: no
HUD lmsensors: no
Shared libs: yes
Static libs: no
Shared-glapi: yes
CFLAGS: -g -O2 -Wall -std=c99
-Werror=implicit-function-declaration -Werror=missing-prototypes
-fno-math-errno -fno-trapping-math
CXXFLAGS: -g -O2 -Wall -fno-math-errno -fno-trapping-math
Macros: -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS
-D_GNU_SOURCE -DUSE_SSE41 -DUSE_GCC_ATOMIC_BUILTINS -DNDEBUG
-DUSE_X86_64_ASM -DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF
-DHAVE_MKOSTEMP -DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM
-DGLX_USE_TLS -DENABLE_SHADER_CACHE -DMESA_EGL_NO_X11_HEADERS
-DHAVE_LLVM=0x0400 -DMESA_LLVM_VERSION_PATCH=0
LLVM_CFLAGS: -I/opt/clang/4.0.0/include
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
LLVM_CXXFLAGS: -I/opt/clang/4.0.0/include -std=c++11
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
LLVM_CPPFLAGS: -I/opt/clang/4.0.0/include
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
LLVM_LDFLAGS: -L/opt/clang/4.0.0/lib
PYTHON2: python2.7
Run 'make' to build Mesa
----------
Chuck Atkins
Staff R&D Engineer, Scientific Computing
Kitware, Inc.
On Fri, May 12, 2017 at 10:25 AM, Patrick Begou <
Patrick.Begou at legi.grenoble-inp.fr> wrote:
> Hi,
>
> I'm still trying to build paraview 5.3 with Qt4.8. As paraview superbuild
> was failing on my desktop (centos 6.9, Nvidia GPU), I build paraview by
> hand and it is running now with and without pvserver connection
> .
> The problem went back with building same paraview version on the cluster
> frontend: CentOS 6.7, no GPU. The compilation is successfull but launching
> paraview I get some errors with OpenGL:
>
> ERROR: In /kareline/data/begou/PARAVIEW5/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 825
> vtkXOpenGLRenderWindow (0x2280fb0): 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.
>
> ERROR: In /kareline/data/begou/PARAVIEW5/paraview/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx,
> line 812
> vtkXOpenGLRenderWindow (0x2280fb0): failed to create offscreen window
>
> ERROR: In /kareline/data/begou/PARAVIEW5/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 813
> vtkXOpenGLRenderWindow (0x2280fb0): GLEW could not be initialized.
>
> I've built and installed mesa from mesa-17.0.4.tar.gz using:
> ./configure \
> PKG_CONFIG_PATH=/share/apps/paraview-5.3.0/lib/pkgconfig \
> --prefix=/share/apps/paraview-5.3.0 \
> --disable-osmesa --enable-gallium-osmesa --enable-gallium-llvm \
> --with-llvm-prefix=/share/apps/paraview-5.3.0
>
> With several requested libraries:
> libxshmfence-1.2.tar.gz
> libxcb-1.12.tar.gz
> libXau-1.0.8.tar.gz
> pthread-stubs-0.3.tar.gz
> xcb-proto-1.12.tar.gz
> libdrm-2.4.70.tar.gz
> llvm-4.0.0.src.tar.xz
> all under /share/apps/paraview-5.3.0/
>
> I've checked with strace that paraview was loading libGL in
> /share/apps/paraview-5.3.0/lib and not the system one, requested by other
> application (frontend is in production and I cannont break these libraries
> used by other softwares).
>
>
> I must confess I'm not familiar at all with these libraries and
> environments, mesa or osmesa, GPU or not GPU, of screen rendering... all
> documentation deeping in obscure details while I'm searching to understand
> these concepts.
> it is clear for me that on the nodes (without GPU) I will use OSMesa and
> no GUI, but on the frontend where I need GUI ???
>
> Thanks for your advices and sorry if this is a very basic lack of
> understanding from myself.
>
> Patrick
>
>
> Paraview cmake is:
> ccmake -DBUILD_SHARED_LIBS=ON \
> -DPARAVIEW_USE_MPI=ON \
> -DCMAKE_BUILD_TYPE=Release \
> -DPARAVIEW_BUILD_QT_GUI=ON \
> -DPARAVIEW_QT_VERSION=4 \
> -DQT_QMAKE_EXECUTABLE=/share/apps/paraview-5.3.0/qt4.8.6/bin/qmake \
> -DPARAVIEW_ENABLE_FFMPEG=ON \
> -DPARAVIEW_ENABLE_PYTHON=ON \
> -DPYTHON_INCLUDE_DIR=/share/apps/python279/include/python2.7 \
> -DPYTHON_LIBRARY=/share/apps/python279/lib/libpython2.7.so \
> -DPYTHON_LIBRARY_DEBUG=/share/apps/python279/lib/libpython2.7.so \
> -DCMAKE_INSTALL_PREFIX=/share/apps/paraview-5.3.0 \
> -DCMAKE_VERBOSE_MAKEFILE=ON \
> -DCMAKE_CXX_COMPILER=/share/apps/GCC485/bin/g++ \
> -DCMAKE_C_COMPILER=/share/apps/GCC485/bin/gcc \
> -DCMAKE_Fortran_COMPILER=/share/apps/GCC485/bin/gfortran \
> -DFFMPEG_ROOT=/share/apps/paraview-5.3.0 \
> -DOPENGL_INCLUDE_DIR=/share/apps/paraview-5.3.0/include \
> -DOPENGL_gl_LIBRARY=/share/apps/paraview-5.3.0/lib/libGL.so \
> ../paraview
>
>
> --
> ===================================================================
> | Equipe M.O.S.T. | |
> | Patrick BEGOU | mailto:Patrick.Begou at grenoble-inp.fr <Patrick.Begou at grenoble-inp.fr> |
> | LEGI | |
> | BP 53 X | Tel 04 76 82 51 35 |
> | 38041 GRENOBLE CEDEX | Fax 04 76 82 52 71 |
> ===================================================================
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170512/ffae59e0/attachment.html>
More information about the ParaView
mailing list