[Paraview] PV 2.0.3 versus Suse Linux 9.3

[Berk Geveci]

ParaView does not specify which X extension to get by name. This is
done by the GL library paraview is linked to. It is possible  that
there is a difference between the libraries the paraview binary is
linked against and the ones specified in Suse. In this case, you have
to compile paraview from source on that platform.

-Berk

On 7/10/05, SamuelKey <samuelkey at comcast.net> wrote:
> There appears to be a naming conflict between
> ParaView (2.0.3) and Xorg's X-window server
> in Suse Linux 9.3
> 
> >From a ParaView "failed" startup I get --
> Xlib:  extension "GLX" missing on display ":0.0".
> Aborted
> 
> >From the /etc/X11/xorg.conf file I have --
> Section "Module"
>   Load         "dbe"
>   Load         "type1"
>   Load         "freetype"
>   Load         "extmod"
>   Load         "glx"
>   Load         "v4l"
> EndSection
> 
> Both files are attached.  My guess at
> what may be the trouble is that ParaView
> is looking for GLX as the extension name,
> and Xorg is using glx as the extension
> name???
> 
> Any suggestions on what I should do?
> 
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
> 
> 
> 
>