From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight <insight@sourceware.org>
Subject: Re: [PATCH] Use system Tcl et al
Date: Sun, 03 Aug 2008 21:51:00 -0000 [thread overview]
Message-ID: <m3y73dpy3e.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m37iaxrf1r.fsf@fleche.redhat.com> (Tom Tromey's message of "Sun\, 03 Aug 2008 14\:58\:56 -0600")
Keith> A clean build of libgui fails with no tcl, tk, itcl? What's the
Keith> failure? Do you have the -devel packages installed?
Tom> Whoops, sorry about that. I had itcl-devel but not the others. I'm
Tom> rebuilding now.
Ok. I deleted tcl,tk,itcl from the source tree. I have
tcl,tk,itcl,iwidgets and -devel packages all installed. I built --
went fine.
However, insight does not start up:
opsy. ./install/bin/insight
Error: Can't find a usable itcl.tcl in the following directories:
/usr/share/itcl3.3 /home/tromey/gnu/baseline-gdb/install/bin/../lib/itcl3.3 /home/tromey/gnu/baseline-gdb/install/bin/../lib64/itcl3.3 /home/tromey/gnu/baseline-gdb/install/bin/../library /home/tromey/gnu/baseline-gdb/install/bin/../../library /home/tromey/gnu/baseline-gdb/install/bin/../../itcl/library /home/tromey/gnu/baseline-gdb/install/bin/../../../itcl/library
This probably means that Itcl/Tcl weren't installed properly.
If you know where the Itcl library directory was installed,
you can set the environment variable ITCL_LIBRARY to point
to the library directory.
That /usr/share is funny ... the file is actually in /usr/lib.
FWIW if I run tclsh and 'package require' each of Itcl,Itk,Iwidgets, it
works just fine.
Tom
prev parent reply other threads:[~2008-08-03 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 22:25 Keith Seitz
2008-08-02 23:46 ` Keith Seitz
2008-08-03 14:06 ` Tom Tromey
2008-08-03 17:41 ` Keith Seitz
2008-08-03 20:59 ` Tom Tromey
2008-08-03 21:51 ` Tom Tromey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3y73dpy3e.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=insight@sourceware.org \
--cc=keiths@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).