itcl in insight

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

itcl in insight

Robert Bu 卜勇华
Hi,

I checked the config log in bundle/libgui. The configure script checked for tcl, tk. However, it seems that it does not check for itcl.
Build and install is OK here on Redhat Enterprise 6.3 (RHEL-6.3, x86_64). When I run insight, it complains:
"Error: can't find package itcl 3.3"

I tried to install itcl 3.3. It is a quite old version and does not compile with my TCL (8.5.7). So I installed itcl 3.4.1. Can I tell insight to use my itcl 3.4.1?

B.R.
Robert

Reply | Threaded
Open this post in threaded view
|

RE: itcl in insight

Patrick Monnerat
 
Robert Bu wrote:
> Hi,
Hi Robert,

> I checked the config log in bundle/libgui. The configure script
checked for tcl, tk. However, it seems that it does not check for itcl.

Insight does not need itcl/itk development files at compile time
anymore. Thus they are not checked. However you must have the runtime
files installed at execution time.

> Build and install is OK here on Redhat Enterprise 6.3 (RHEL-6.3,
x86_64). When I run insight, it complains:
> "Error: can't find package itcl 3.3"

> I tried to install itcl 3.3. It is a quite old version and does not
compile with my TCL (8.5.7). So I installed itcl 3.4.1. Can I tell
insight to use my itcl 3.4.1?

The "3.3" is now only the lower version you need. Since Feb 16, insight
is more tolerant about versions and package name spellings. If you have
git-pulled it recently, it can only be a path problem, not under control
of insight.

Try:
$ wish
% package require itcl
...     <-- here you have either an error or the itcl installed version.
% package require Itcl
...     <-- here you have either an error or the Itcl installed version.

If both fail, this is definitely a path problem in one of tcl or itcl
RHEL package.

Patrick
Reply | Threaded
Open this post in threaded view
|

RE: itcl in insight

Robert Bu 卜勇华
In reply to this post by Robert Bu 卜勇华
Hi Patrick,

RHEL has no pre-built package for itcl.
I installed itcl3.4 by "configure; make all; make install". But tcl cannot find it.  I tried to modify tclConfig.sh to tell tcl the package path of itcl. It fails.
Finally, I added the package loading script to tk/pkgIndex as following. Then everything works fine. Thank you for your help.

# Robert: cannot tell tcl the path of itcl. So I add it here
if {![package vsatisfies [package present Tcl] 8.5]} {return}
package ifneeded Itcl 3.4 [list load [file join $dir .. itcl3.4 "libitcl3.4.so"] Itcl]

package ifneeded Itk 3.4 [list load [file join $dir .. itk3.4 "libitk3.4.so"] Itk]

package ifneeded Iwidgets 4.0.0 [list source [file join $dir .. iwidgets4.0.0 iwidgets.tcl]]

Best regards.
Robert Bu
 
-----Original Message-----
From: Patrick Monnerat [mailto:[hidden email]]
Sent: Wednesday, March 11, 2015 9:34 PM
To: Robert Bu; [hidden email]
Subject: RE: itcl in insight

 
Robert Bu wrote:
> Hi,
Hi Robert,

> I checked the config log in bundle/libgui. The configure script
checked for tcl, tk. However, it seems that it does not check for itcl.

Insight does not need itcl/itk development files at compile time anymore. Thus they are not checked. However you must have the runtime files installed at execution time.

> Build and install is OK here on Redhat Enterprise 6.3 (RHEL-6.3,
x86_64). When I run insight, it complains:
> "Error: can't find package itcl 3.3"

> I tried to install itcl 3.3. It is a quite old version and does not
compile with my TCL (8.5.7). So I installed itcl 3.4.1. Can I tell insight to use my itcl 3.4.1?

The "3.3" is now only the lower version you need. Since Feb 16, insight is more tolerant about versions and package name spellings. If you have git-pulled it recently, it can only be a path problem, not under control of insight.

Try:
$ wish
% package require itcl
...     <-- here you have either an error or the itcl installed version.
% package require Itcl
...     <-- here you have either an error or the Itcl installed version.

If both fail, this is definitely a path problem in one of tcl or itcl RHEL package.

Patrick
Reply | Threaded
Open this post in threaded view
|

RE: itcl in insight

Patrick Monnerat
 
Robert Bu wrote:

> RHEL has no pre-built package for itcl.

You might consider enabling EPEL repository: among others it provides
itcl, itk and iwidgets for RHEL.
http://www.rackspace.com/knowledge_center/article/install-epel-and-addit
ional-repositories-on-centos-and-red-hat

Sorry, I cant try here: I have no such system installed.

Patrick
Reply | Threaded
Open this post in threaded view
|

RE: itcl in insight

Robert Bu 卜勇华
I tried your method. That's great.

However, is that possible to install dependent tcl packages with insight?  So that I can run insight on the host even if there's no Itcl related on that host.

Best regards.
Robert Bu 


-----Original Message-----
From: Patrick Monnerat [mailto:[hidden email]]
Sent: Thursday, March 12, 2015 9:53 PM
To: Robert Bu; [hidden email]
Subject: RE: itcl in insight

 
Robert Bu wrote:

> RHEL has no pre-built package for itcl.

You might consider enabling EPEL repository: among others it provides itcl, itk and iwidgets for RHEL.
http://www.rackspace.com/knowledge_center/article/install-epel-and-addit
ional-repositories-on-centos-and-red-hat

Sorry, I cant try here: I have no such system installed.

Patrick
Reply | Threaded
Open this post in threaded view
|

RE: itcl in insight

Patrick Monnerat
 
Robert Bu wrote:

> I tried your method. That's great.

:-)

> However, is that possible to install dependent tcl packages with
insight?  So that I can run insight on the host even if there's no Itcl
related on that host.

Not anymore: the last version of insight does not bundle tcl/tk/etc
anymore and only relies on preinstalled packages.
Sometimes ago, there was an insight rpm package in EPEL, but I think the
maintainer has dropped it. You might re-create an rpm spec file for it
with dependencies to itcl, itk, iwidgets, etc and use "yum localinstall"
on the platforms you want to install it. Doing so will pull the proper
packages in.
I'm the packager for Fedora, but I do not plan to maintain an insight
EPEL package myself.
Here is the current spec file for Fedora:
http://pkgs.fedoraproject.org/cgit/insight.git/tree/insight.spec
You can use it as a starting point for your custom RHEL package. But
you'll need to adapt it: it is 6 month old :-/

Cheers,
Patrick