dorsal team mailing list archive

[Douglas N Arnold <arnold@xxxxxxx>]

Dear Johannes:  Thanks for your continuing help with this.  I can now
build dolfin, including vtk and viper, under Scientific Linux 6.
However viper does not work because of some VTK library problem.
When I enter "from dolfin import *" I get

> *** Warning: /home/faculty/arnold/workshop/FEniCS-sl6/lib/python2.6/site-packages/VTK-5.6.1-py2.6.egg/vtk/libvtkIOPython.so: undefined symbol: PyVTKClass_vtkMPASReaderNew
> *** Warning: Unable to import Viper, plotting disabled.

At least this is a different undefined symbol error than I had when I
started :)

This is a big problem, which probably affect Red Hat Linux Enterprise
and CentOS 6, as well as Scientific Linux 6, since they are practically
identical.  I am eager to find a fix, so further suggestions are very
welcome.

Here is the platform file I used, which works except for this issue.


# Red Hat Enterprise Linux 6/CentOS 6/Scientific Linux 6

# This build script assumes that you have several packages already
# installed via Fedora's yum using the following command:
#
# su -c 'yum install -y wget bzr pkgconfig libxml2-devel gcc gcc-c++ \
# openmpi-devel openmpi numpy swig boost-devel atlas-devel blas-devel \
# lapack-devel python-devel cmake mpfr-devel gmp-devel cppunit-devel'
#
# Also, if you have multiple MPI libraries installed, make sure the
# appropriate version is selected. For this, on a 32-bit operating
# system, run:
#
# module load openmpi-i386
#
# or on a 64-bit operating system, run:
#
# module load openmpi-x86_64
#
# If you are using SELinux, you may need to disable it to run DOLFIN
# programs.
##

# Platform specific variables
default PETSC_ARCH=linux-gnu-cxx-opt
default SCOTCH_ARCH=pc_linux2

# Define the packages this platform needs
PACKAGES=(
cmake
vtk
parmetis
scotch
trilinos
petsc
slepc
armadillo
cgal
scientificpython
fiat
ferari
ufc
ufl
ffc
viper
instant
dolfin
)



On 08/06/2011 04:34 PM, Johannes Ring wrote:
> Douglas,
>
> On Fri, Aug 5, 2011 at 9:59 PM, Douglas Arnold<arnold@xxxxxxx>  wrote:
> > Thanks for this reply.  I tried adding vtk to the platform file right after
> > cmake
> > and ran into a problem I do not understand.  After dorsal builds cmake, then
> > it downloads vtk-5.6.1 and unpacks it, but as soon as it starts to build
> > vtk,
> > it pops up a cmake screen asking me to configure it, which I don't know how
> > to
> > do.  (The screen looks like this:
> >
> > >                                                      Page 0 of 1
> > >   EMPTY CACHE
> > >
> > > EMPTY CACHE:
> > > Press [enter] to edit option                                CMake Version
> > > 2.6 - patch 4
> > > Press [c] to configure
> > > Press [h] for help         Press [q] to quit without generating
> > > Press [t] to toggle advanced mode (Currently Off)
> >
> > Any suggestions?
>
> Yes. I recently changed this in Dorsal. If you are using the
> development version of Dorsal, simply do "bzr pull" in the Dorsal
> directory and then run Dorsal again. If not, do "bzr branch lp:dorsal"
> to fetch the development version and try building it from there.
>
> Johannes