[Paraview] TCLLIBPATH

Kevin H. Hobbs kevin.hobbs.1 at ohiou.edu
Wed May 10 10:38:21 EDT 2006


It seems ParaView from today's CVS does not respect TCLLIBPATH again.

export TCLLIBPATH=/home/kevin/kitware/ParaView_Build/lib/tcl8.4/
[kevin at gargon ParaView_Build]$ paraview
ParaView error: InitializeTcl failed
Tcl_Init error: Can't find a usable init.tcl in the following
directories:
    /usr/local/lib/tcl8.4 /home/kevin/kitware/lib/tcl8.4 /home/kevin/lib/tcl8.4 /home/kevin/kitware/library /home/kevin/library /home/kevin/tcl8.4.5/library /home/tcl8.4.5/library /usr/local/lib/tcl8.4



This probably means that Tcl wasn't installed properly.


The full path to paraview in the builddir works though. There is a bug
on this, #2750. The OP says he was told it was fixed in CVS. My last
build from CVS was quite a while ago, weeks maybe months, and it
respected TCLLIBPATH.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://public.kitware.com/pipermail/paraview/attachments/20060510/e98a4d7b/attachment.pgp


More information about the ParaView mailing list