From: Gene Smith <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: Using system tcl/tk version 8.5
Date: Fri, 19 Mar 2010 07:10:00 -0000 [thread overview]
Message-ID: <hnuuo5$17e$1@dough.gmane.org> (raw)
I followed these instructions from Keith on how to build (cvs head)
insight w/o using the included tcl/tk:
<quoth Keith from 3-18-2010>
To build using the system-supplied tcl/tk, make sure you have the dev
packages (on linux) installed: tcl-devel, tk-devel, itcl-devel,
itk-devel. Remove (or rename) tcl, tk, and itcl from your source
directory, and the build will find the system-installed versions. [I
don't recall if this is absolutely necessary, but I do it anyway.]
When starting an untested build configuration for the first time, I
usually do a "make configure-gdb" and check the output of configure that
it found the tcl/tk/itcl/itk stuff that I expected it to.
<end quote>
I did what he said in the first paragraph but my system (fedora 12) has
tk/tcl 8.5 and the build process expects 8.4. But if I rename my
installed libtcl8.5.so and libtcl8.5.so to 8.4 the link works.
But when I run insight it expects 8.5 again so it fails to run. But if I
rename the system files above back to 8.5 it runs.
Is there a way to specify in configure the version of tcl/tk that you
have on your system or, even better, to try to work with whatever you have?
Regarding his 2nd paragraph above, where do you run the "make
configure-gdb" he speaks of? It does not seem to be a supported target.
-gene
next reply other threads:[~2010-03-19 4:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 7:10 Gene Smith [this message]
2010-03-19 9:02 ` Keith Seitz
2010-03-21 5:49 ` Gene Smith
[not found] ` <4BB2DF85.10208@redhat.com>
2010-04-01 3:15 ` Gene Smith
2010-04-05 3:00 ` Gene Smith
2010-04-07 3:12 ` Gene Smith
2010-04-09 4:13 ` Gene Smith
2010-04-09 20:33 ` Gene Smith
2010-05-20 2:14 ` Gene Smith
2010-03-23 2:47 ` Gene Smith
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='hnuuo5$17e$1@dough.gmane.org' \
--to=gds@chartertn.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).