From: Keith Seitz <keiths@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: insight <insight@sourceware.org>
Subject: Re: [PATCH/itcl] Fix itkConfig.sh
Date: Sat, 02 Aug 2008 21:30:00 -0000 [thread overview]
Message-ID: <4894D1BD.308@redhat.com> (raw)
In-Reply-To: <m3zlnvun55.fsf@fleche.redhat.com>
Tom Tromey wrote:
> Unfortunately now it won't start:
>
> opsy. ./gdb
> ./gdb: error while loading shared libraries: libitcl3.3.so: cannot open shared object file: No such file or directory
Yeah, you're going to need to add those to LD_LIBRARY_PATH... Or maybe I
could add something to gdbtk_init to do that for us? I guess I'll get to
that when I'm "finished" with ripping it out.
FWIW, I do not plan to use the in-tree tcl, tk, and itcl anymore. Only
the system-supplied ones. I (will) consider building insight with
src/tcl, src/tk, and src/itcl deprecated. Hopefully, in a few hours. :-)
> The shared libraries are installed in install/lib/itk3.3 and
> install/lib/itcl3.3. I think just install/lib would be preferable.
This is where the upstream sources put them since Itcl and Itk are now
using the TEA. I am hesitant (but not unwilling) to change this if there
is need.
> Also, it seems to me that the test suite ought to set LD_LIBRARY_PATH
> somewhere. I didn't see anything for this; without it, 'make check'
> fails a lot.
Ugh. I didn't even consider that. Hacking gdbtk_init for LD_LIBRARY_PATH
sounds more and more like a better idea: it kills two birds with one stone.
> Is there some other way I ought to be doing this? Like, maybe I
> should just install the system itcl... ?
Well, for my sanity, I would recommend that you switch to installing
system tcl, tk, and itcl when I commit the final changes. It'll mean
less work for me! :-P
Won't be long now...
Keith
prev parent reply other threads:[~2008-08-02 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 20:36 Keith Seitz
2008-08-02 21:24 ` Tom Tromey
2008-08-02 21:30 ` Keith Seitz [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=4894D1BD.308@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=tromey@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).