From: Keith Seitz <keiths@redhat.com>
To: sandip gangakhedkar <sandipfloyd@gmail.com>
Cc: insight@sourceware.org
Subject: Re: make fails on ubuntu 11.04 VM,
Date: Fri, 04 Nov 2011 04:18:00 -0000 [thread overview]
Message-ID: <4EB36769.20903@redhat.com> (raw)
In-Reply-To: <CAEPsib3_m+CcBQHDNSuRWG4yxkagx0s_PxL-BOeYhEoY_qwYLg@mail.gmail.com>
On 11/03/2011 08:53 PM, sandip gangakhedkar wrote:
> In my distro (ubuntu), Tk is located at /usr/share/tcltk/tk8.4 so I
> added this path to the env variable TK_LIBRARY, but the error
> persists. Can someone point out what I am doing wrong here?
For that version of Insight (6.8 -- *ancient*, but I have not done a
release since then), you will need to use the in-tree tcl/tk/itcl.
If you want to use your system's tcl & tk (which is what I use), you
must checkout the development sources from sourceware.org.
That error message is typical of conflicts arising when the build has
erroneously picked up tclConfig.sh from your system instead of the
in-tree version. I don't recall if that is a bug that has been fixed in
the (almost) three years since the 6.8 release.
Like I said, I use CVS HEAD gdb/insight with a patch (not committed) to
build on x86_64.
Keith
next prev parent reply other threads:[~2011-11-04 4:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEPsib3XCnbO1yK49NQDp1QFQJVYamgBR1nQL1vAL7+HGVMKfw@mail.gmail.com>
2011-11-04 1:12 ` sandip gangakhedkar
2011-11-04 1:37 ` Keith Seitz
2011-11-04 2:47 ` sandip gangakhedkar
2011-11-04 3:54 ` sandip gangakhedkar
2011-11-04 4:18 ` Keith Seitz [this message]
2011-11-04 17:09 ` sandip gangakhedkar
2011-11-04 18:32 ` Keith Seitz
[not found] ` <4EB43706.8020509@redhat.com>
[not found] ` <CAEPsib1LCq-RTQrsdPwruOS7P-6mrig=SSO09KO+EjThGpphHw@mail.gmail.com>
[not found] ` <4EBBFDB3.2010404@redhat.com>
2011-11-10 19:55 ` sandip gangakhedkar
2011-11-10 20:06 ` Keith Seitz
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=4EB36769.20903@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=sandipfloyd@gmail.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).