It must be some part of our build process. If we download the
precompiled Paraview executable, it works fine. If I do a generic
build using the source code, it also works. So, there must be some
flag or something in our production build tree that's causing a problem
with the nVidia 180-xx drivers.
Berk Geveci wrote:
Huh, that's weird. vtkSMExtractDocumentation links against OpenGL but
does not make any OpenGL calls. Can you build debug and try to get a
stack trace?
-berk
On Tue, Jan 27, 2009 at 2:54 PM, Rick Angelini <[email protected]> wrote:
Has anyone had any trouble building Paraview with the latest nVidia GL
libraries? On both RH4 and RH5, we've not been able to compile Paraview
3.4.0 (or 3.2.1) against nVidia driver 180.22 or 180.25. We can build
against nVidia driver 173.14.xx. Also, if we build on a system that has
driver 173.14.xx and then try to execute 'paraview' on a system with a
180.22 driver, we also get a floating point exception error.
The compile failure is a floating point exception and looks like this:
[89%] Built target pvpython-real
Scanning dependencies of target pvbatch
Scanning dependencies of target pvpython
/bin/sh: line 1: 28655 Floating point
exception../../bin/vtkSMExtractDocumentation
/build/ParaView-3.2.1-x86_64-RHEL/Documentation
/build/src/ParaView3.2.1/Qt/Components/Resources/XML/ParaViewWriters.xml
make[2]: *** [Documentation/ParaViewWriters.html] Error 136
make[1]: *** [Servers/ServerManager/CMakeFiles/HTMLDocumentation.dir/all]
Error 2
make[1]: *** Waiting for unfinished jobs....
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
