vtk version inconsistency in vtk.package

Bug #931715 reported by Ji Peng
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Dorsal
Invalid
Undecided
Unassigned

Bug Description

FEniCS/packages/vtk.package

SOURCE=http://www.vtk.org/files/release/5.8/
PACKING=.tar.gz
BUILDCHAIN=cmake
EXTRACTSTO=VTK
PROCS=1

CONFOPTS="-D CMAKE_BUILD_TYPE:STRING=Release
          -D BUILD_TESTING:BOOL=OFF
          -D BUILD_SHARED_LIBS:BOOL=ON
          -D VTK_WRAP_PYTHON:BOOL=ON
          -D VTK_USE_TK:BOOL=ON
          -D VTK_USE_GL2PS:BOOL=ON"

if [ -d "${VTK_DATA_ROOT}" ]; then
    CONFOPTS="${CONFOPTS} -D VTK_DATA_ROOT:PATH=${VTK_DATA_ROOT}"
fi

package_specific_setup () {
    chmod 600 Utilities/vtktiff/tif_fax3sm.c
}

package_specific_register () {
    export LD_LIBRARY_PATH=${INSTALL_PATH}/lib/vtk-5.6:${LD_LIBRARY_PATH}
    export DYLD_LIBRARY_PATH=${INSTALL_PATH}/lib/vtk-5.6:${DYLD_LIBRARY_PATH}
}

The source is 5.8, but when it exports vtk, it's vtk-5.6. However, in build script, there is a line saying
# Once you've set up VTK, you need to manually set the following
# environment variable in order for Viper to find it:
#
# export LD_LIBRARY_PATH=${INSTALL_PATH}/lib/vtk-5.4:${LD_LIBRARY_PATH}

Based on my personal experience, only exporting vtk-5.8 can make dolfin successfully built.

Revision history for this message
Johannes Ring (johannr) wrote :

Thanks for the report, but this has already been fixed in the development version.

Changed in dorsal:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.