[Paraview] Paraview v3.10.1/0 segmentation fault with MPI and MESA support on.

[Kevin H. Hobbs]

On 04/19/2011 12:29 PM, Albina, Frank wrote:
> Dear Kevin!
> 
> To put things more clearly and to avoid confusion, I'd like to build a paraview v3.10.x executable with X. In this regard, I'd like to use paraview as the client and start remotely the paraview server with mpirun -np <N> --use-offscreen-rendering.

I build paraview with X and the accelerated drivers for my graphics card
and pvserver with OSMesa and MPI.

I start paraview on my workstation and pvserver on our cluster.

> I *should* be able to build paraview with X using offscreen rendering, based on the MESA libraries.

Yes, you can but three of these terms are not precise enough to be
useful in this conversation:
  Paraview
    paraview
    pvbatch
    pvserver
  Offscreen
    with X and hardware
    with X
    without X
  Mesa
    hardware accelerated DRI drivers
    xlib drivers
    OSMesa needs GL
    OSMesa conflicts with GL


 Again, this worked with paraview v3.8.1, but I fail getting it up and
running with paraview 3.10.x performing the same configuration steps as
with paraview 3.8.1.
> 

Parview may have adapted to the requirements of the newer OSMesa
Library. I do not really know without knowing *exactly* what you were
and are doing.

> If I understood you well, one cannot link an application to libOSMESA.so and libGL.so/libGLU.so at the same time.

Older versions of Mesa could produce an OSMesa library that had to be
linked to Mesa's GL library ( so long as that GL library was not built
with hardware acceleration support ) *or* they could produce an OSMesa
library that did not depend on GL (or X) and could not be linked with
any other GL library.

Newer versions of Mesa only produce an OSMesa that does not depend on GL
(or X) and can not be linked with any other GL library.

I link to the libGLU.so produced along with libOSMesa.so all the time.

 If this is correct, then it would explain why I get a segmentation
fault straight away.

I believe it does.

 On the other hand, what are then the libGL.so and libGLU.so one has to
link against, if not the ones from MESA v7.x according to the WIKI:

That depends.

[ big snip ]

Sorry, I can't really respond to most of that right now.

> 
> 
> Thank you very for your help anyway and please let me know if you have made any progress with building paraview on your cluster.

I build the development versions every night so it shouldn't be too much
trouble. I'm just putting *everything* together in one script (well
really just a sequence of commands) adjusted for release versions,
installed to /opt, and so on.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
URL: <http://www.paraview.org/pipermail/paraview/attachments/20110419/f00ed684/attachment.pgp>