[vtkusers] Installation Problems on Redhat 6.2

Dave Reed dreed at capital.edu
Tue Jun 13 16:35:21 EDT 2000


> From: Timothy Perla <tjp2 at msr.epm.ornl.gov>
> 
> Can someone please lend me their expertise on installing vtk 3.1 on redhat
> linux 6.2.
> I have downloaded and installed tcl 8.3.1 and tk 8.3.1, as well as mesa 3.0-2
> and mesa-devel 3.0-2.  MPI is also running on the system.  
> I'm fairly certain my user.make is set up correctly, but about one half hour
> into the compile I get the following message:
> 
> 
> gmake[1]: Entering directory `/usr/src/redhat/SOURCES/vtk/tcl'
> c++ -o vtk tkAppInit.o \
> -L. -g -O2  -DVTK_USE_PTHREADS -D_HP_NO_FAST_MACROS -DHAVE_LIMITS_H -DHAVE_UNISTD_H -I. -I./../common -I/usr/src/TclTk/tk8.3.1/generic
> -I/usr/local/src/TclTk/tcl8.3.1/generic -DVTK_USE_TKWIDGET -DVTK_USE_OGLR -I/usr/X11R6/include   -I/usr/X11R6/include -I/usr/local/mpich-1.2.0/include -DVTK_USE_MPI -I./../graphics -DVTK_USE_GRAPHICS -I./../imaging -DVTK_USE_IMAGING -I./../patented -DVTK_USE_PATENTED -I./../contrib -DVTK_USE_CONTRIB  -rdynamic   -L/usr/src/redhat/SOURCES/vtk/contrib -lVTKContribTcl -lVTKContrib  -L/usr/src/redhat/SOURCES/vtk/patented -lVTKPatentedTcl -lVTKPatented -L/usr/src/redhat/SOURCES/vtk/imaging -lVTKImagingTcl -lVTKImaging -L/usr/src/redhat/SOURCES/vtk/graphics -lVTKGraphicsTcl -lVTKGraphics -L../common -lVTKCommonTcl -lVTKCommon -L/usr/X11R6/lib -lGL /usr/local/mpich-1.2.0/lib/libmpich.a /usr/local/mpich-1.2.0/lib/libpmpich.a /usr/local/lib/libtk.so /usr/local/lib/libtcl.so -ldl -lpthread \
> -L/usr/X11R6/lib -lXext -lXt -lSM -lICE -lX11  -lm
> /usr/bin/ld: cannot find -lGL
> collect2: ld returned 1 exit status
> gmake[1]: *** [vtk] Error 1
> gmake[1]: Leaving directory `/usr/src/redhat/SOURCES/vtk/tcl'
> gmake: *** [build_tcl] Error 2 
> 
> 
> Does this look familiar to anyone?  Thanks.

RH 6.2 should already have tcl/tk and Mesa 3.2.  If you really
installed Mesa 3.0, the OpenGL library may be called MesaGL.  I know
it was in the Mesa 2.x series and I think it was only recently that
Mesa started calling the GL instead of MesaGL.  You could make a
symbolic link from libGL.so to libMesaGL.so and that will probably fix
it.  I would recommend the more recent version of Mesa (3.2) instead
of 3.0 if that's really what you have.

Dave




More information about the vtkusers mailing list