[vtkusers] Fixed: compiling with mpi support

[Stanley Dunn]

On Thu, 27 Jul 2000, Randy Heiland wrote:

> Why not contribute a bit more info to the archive than that?  Like,
> what'd you do?

Sorry, Randy et al.  I got too busy playing.  Here is what I did:

Recap:  The problem was compiling vtk with mpi support. I get through just
about everything until I get to generating libVTKContribPython.so where I
get the following error:
 
 /usr/bin/ld: libVTKContribPython.so: undefined versioned symbol name fork@@GLIBC_2.0 
 /usr/bin/ld: failed to set dynamic section sizes: Bad value
 collect2: ld returned 1 exit status                                

Fix:  Edit Kits.make, in the python rules section for libVTK$(ME)Python. 
I added ${CONTROLLER_API_LIBS} as follows:

libVTK$(ME)Python$(SHLIB_SUFFIX): python/${ME}Init.o ${KIT_OBJ} \
        ${PYTHON_O_ADD} ${PYTHON_WRAP}
        rm -f libVTK$(ME)Python$(SHLIB_SUFFIX)
        $(CXX) ${CXX_FLAGS} ${VTK_SHLIB_BUILD_FLAGS} \
        -o libVTK$(ME)Python$(SHLIB_SUFFIX) python/${ME}Init.o \
          ${KIT_OBJ} ${PYTHON_O_ADD} ${PYTHON_WRAP} \
        -L. ${XLDFLAGS} ${PYTHON_LIBS} ${CONTROLLER_API_LIBS} \
        ${XLIBS} -lXext -lXt ${X_PRE_LIBS} -lX11 ${X_EXTRA_LIBS}  ${DL_LIBS} \
        ${THREAD_LIBS} 

to generate libVTKContribPython.so with the mpi support.  I think this
change will not affect non-mpi versions, although I haven't verified that.

Stan