From: James Ingham <jingham@cygnus.com>
To: Erik Sobel <erik.sobel@alphatech.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: problems installing on solaris
Date: Tue, 26 Oct 1999 12:40:00 -0000 [thread overview]
Message-ID: <14358.1078.87963.811650@leda.cygnus.com> (raw)
In-Reply-To: <4.2.0.58.19991026150948.00a7c200@mail.alphatech.com>
Erik,
Did you actually install insight, or did you just run it from the
build tree?
The init.tcl that you want should be in prefix/share/tcl in the
installed version of the software.
Two things to note:
1) You have to use the version of Tcl/Tk that comes with gdb for now.
You can't use one of the Scriptics versions.
2) On some systems, to run from the build tree you have to actually be
in the directory where the gdb executible is.
Jim
You can run gdb from the build tree, but this is somewhat flakier tha
> Thanks for your responses. I updated from 8.0.2 to 8.2, then re-installed
> insight, but still got the same error. I looked in
> /insight/tcl/library/init.tcl (not int.tcl) and found the proc
> tcl_findLibrary but I don't know which library it is supposed to end up in
> and whether it is on my path.
>
> I also verified that I have no TCL_LIBRARY or TK_LIBRARY variables in my
> environment.
> -Erik
>
>
> At 10:23 AM 10/26/99 -0400, you wrote:
> >On 26 Oct, Erik Sobel wrote:
> > > I just did a fresh install of insight on solaris. When I try to
> > execute it
> > > I get the following error
> > >
> > > "Tk_Init failed: invalid command name "tcl_findLibrary"
> > >
> > > Does anyone know how to fix it? Sounds like a path issue or possibly a
> > > Tcl/Tk version issue?
> > >
> >
> >Yes. According to the changes file, the first correct implementation of that
> >function would be in 8.0.4. It's defined in the int.tcl file.
> >
> >L
> >
> >--
> >Penguin Power!
> >
> >Laurent Duperval
> >CGI - FWFM Project
> >Phone: (514) 350-3368
> > mailto:laurent.duperval@cgi.ca
>
> ----------------------------------------------------------------------------
> ------------------------------
> Erik Sobel
> esobel@alphatech.com
> erik.sobel@alphatech.com
> ----------------------------------------------------------------------------
> ------------------------------
>
--
++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++
Jim Ingham jingham@cygnus.com
Cygnus Solutions Inc.
next prev parent reply other threads:[~1999-10-26 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-26 7:16 Erik Sobel
1999-10-26 7:23 ` laurent.duperval
1999-10-26 12:22 ` Erik Sobel
1999-10-26 12:38 ` laurent.duperval
1999-10-26 12:40 ` James Ingham [this message]
1999-10-26 13:09 ` laurent.duperval
1999-10-26 9:30 ` James Ingham
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=14358.1078.87963.811650@leda.cygnus.com \
--to=jingham@cygnus.com \
--cc=erik.sobel@alphatech.com \
--cc=insight@sourceware.cygnus.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).