Are you using the stock 7.5.1 source code of Mesa?
Yes, I was but I recently updated to Mesa 7.7.
Could you also post the compiler flags and
configure options you use for mesa?
There are two ways to build Mesa. The autotools way and the old way. By
autotools way I mean "./configure && make && make install", and by old
way I mean the canned configurations that come with mesa. I have always
used the old way with success. Do a fresh untar of mesa cd in and type
make. You'll see a list of available configurations. I have used both
"linux" and "linux-x86-64" with success. You can take a look at the
files with these names in the configs directory to see what flags are
being used. To install you'll have to set the INSTALL_DIR variable in
configs/default.
Maybe if I mirror your settings, it will
work here as well.
if this is really an interaction with OpenMPI, rebuilding osmesa may not
make a bit of difference. In that case you might want to try mpich2,
just to see what happens. And if you do I'd suggest you build it yourself.
With ParaView and all of its external dependencies, such as MPI and
OSMesa, I would recommend against system wide installs (eg /usr) . Build
them yourself and install them in a non-standard location (has to be
mounted on all nodes), either /opt/APPNAME or
/home/YOURNAME/apps/APPNAME or something like that, and prior to
building or running ParaView explicitly prepend these locations to
LD_LIBRARY_PATH. The Modules program makes this type of thing very
convenient. This helps CMake find what you want and you're always
absolutely sure that you have the right libraries at run time, and you
can quickly swap them in and out supporting multiple configurations.
Take this last bit of advise with a grain of salt, as I don't want to
sidetrack you from the real issue. If you're not installing PV and just
running it from the build dir, by default he uses RPATH, so run time
library issues won't come up.
Bart Janssens wrote:
On Saturday 06 February 2010 04:09:41 am you wrote:
maybe I shouldn't have opened my mouth, mixing libraries doesn't
necessarily explain the more than 4 procs thing... unless when you run
with 4 procs they are being scheduled to the same node, and running with
more causes another node to come into the mix.
How are process being assigned to nodes?
Hi,
Thanks for the suggestions, but unfortunately I haven't gotten to the point of
running on nodes yet. Everything runs on the head node, which uses custom mesa
and OSMesa RPMs built from the 7.6.1 Mesa source code installed to /usr.
Are you using the stock 7.5.1 source code of Mesa? I have only tried 6.5.1
(CentOS 5.4 flavor) and 7.6.1 so far. Could you also post the compiler flags and
configure options you use for mesa? Maybe if I mirror your settings, it will
work here as well.
Cheers,
_______________________________________________
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://www.paraview.org/mailman/listinfo/paraview
