From: Keith Seitz <keiths@redhat.com>
To: "Kingston Co." <freddie@sb.net>
Cc: insight@sources.redhat.com
Subject: Re: Insight Configuration Problems
Date: Mon, 12 Sep 2005 16:12:00 -0000 [thread overview]
Message-ID: <4325A8CE.60109@redhat.com> (raw)
In-Reply-To: <61972A9D-3CA7-4845-9CF7-D16AF8167975@sb.net>
Kingston Co. wrote:
> Printed in the directions for building and installing insight it states:
> Right now, Insight MUST be built using the versions of Tcl, Tk, Itcl,
> and Tix that come with the sources.
> My question is: I found Tcl, Tk, and Itcl in the source distribution,
> but Tix is missing. Which version of Tix do I download and install for
> Insight to work properly? Are there any special instructions about Tix
> that I need to know in order to install it correctly?
Hi,
Sadly, the documentation is incorrect, and has been for some time. [I'm
not entirely sure how long.]
As it is, when you checkout Insight from CVS (or download a snapshot),
you will get everything you need to build Insight, including tcl, tk,
itcl, and libgui.
Although the goal is to get rid of the dependency on our built-in
versions of tcl, tk, and itcl for "standard" releases, we're not quite
there yet. Actually, I bet we're *awfully* close. Just a lot of
configury changes need to be made, I think; this has been true for some
time since we moved to more standard versions of tcl, tk, and itcl in
the repository.
One of these days, I'm gonna hack the configury to allow us to build
using pre-installed versions of these things.
Keith
next prev parent reply other threads:[~2005-09-12 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 16:04 Kingston Co.
2005-09-12 16:12 ` Keith Seitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-28 5:48 Insight configuration problems Kingston Co.
2005-08-28 10:43 ` E. Weddington
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=4325A8CE.60109@redhat.com \
--to=keiths@redhat.com \
--cc=freddie@sb.net \
--cc=insight@sources.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).