From: Keith Seitz <keiths@redhat.com>
To: Gene Smith <gds@chartertn.net>
Cc: insight@sources.redhat.com
Subject: Re: Using system tcl/tk version 8.5
Date: Fri, 19 Mar 2010 09:02:00 -0000 [thread overview]
Message-ID: <4BA3233C.9090604@redhat.com> (raw)
In-Reply-To: <hnuuo5$17e$1@dough.gmane.org>
On 03/18/2010 09:32 PM, Gene Smith wrote:
> 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.
I use Fedora 11 (soon 13) with Tcl 8.5 (don't forget all the -devel RPMS
on Red Hat-like systems):
tcl-8.5.6-6.fc11.i586
tcl-devel-8.5.6-6.fc11.i586
tk-8.5.6-4.fc11.i586
tk-devel-8.5.6-4.fc11.i586
itcl-3.4-4.fc11.i586
itcl-devel-3.4-4.fc11.i586
itk-3.4-4.fc11.i586
itk-devel-3.4-4.fc11.i586
iwidgets-4.0.2-2.fc11.noarch
Are you using x86_64? I believe I am sitting on a patch to fix some bad
assumptions with that... Still need to test them some more, though.
> 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.
Yeah, definitely cannot do that...
> 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?
You can use:
--with-tcl directory containing tcl configuration
(tclConfig.sh)
--with-tk directory containing tk configuration
(tkConfig.sh)
Normally, you only need to use --with-tcl -- the configury will assume
that tkConfig.sh is in the same place. I believe I tested all this when
I did this work a while ago, but I might have missed something. Testing
three different configury scenarios can get a little confusing.
> 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.
Do "make configure-gdb" just after you do the configure. This is how I
normally do it (when I do configure-gdb instead of all-gdb):
$ CFLAGS="-g" ../src/configure --prefix=/home/keiths/insight/HEAD/built
[snip]
$ make configure-gdb
[now you can check the configure log in gdb/]
$ make all-gdb
What version of insight are you trying to build, BTW. It might make a
difference. [It might not, either. I remember fixing some build bugs a
while ago...]
I've built Insight this way for almost two-three years now, and I've
used the resulting executable for my daily work on archer, so it can be
done.
Keith
next prev parent reply other threads:[~2010-03-19 7:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 7:10 Gene Smith
2010-03-19 9:02 ` Keith Seitz [this message]
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=4BA3233C.9090604@redhat.com \
--to=keiths@redhat.com \
--cc=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).