public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: sandip gangakhedkar <sandipfloyd@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: make fails on ubuntu 11.04 VM,
Date: Fri, 04 Nov 2011 17:09:00 -0000	[thread overview]
Message-ID: <CAEPsib3bd-MX_snCM5NKcrqxMjLsykqac20brSuAK-b9OFQamw@mail.gmail.com> (raw)
In-Reply-To: <4EB36769.20903@redhat.com>

Hi,

Thanks for your reply. Just to confirm that I'm doing it right this
time: I've downloaded the CVS head version -
insight-weekly-CVS-7.0.50-20091130.tar.bz2 from
ftp://sourceware.org/pub/insight/snapshots/current/. Is this is
working version? I see that there is no uninstall script for the
release version. What is the best way to completely remove the
installed version without creating any problems for the new
installation?

Also, should I file a bug for the release version?

-Sandip


On Fri, Nov 4, 2011 at 5:17 AM, Keith Seitz <keiths@redhat.com> wrote:
> 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
>



-- 
-Sandip-

  reply	other threads:[~2011-11-04 17:09 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
2011-11-04 17:09           ` sandip gangakhedkar [this message]
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=CAEPsib3bd-MX_snCM5NKcrqxMjLsykqac20brSuAK-b9OFQamw@mail.gmail.com \
    --to=sandipfloyd@gmail.com \
    --cc=insight@sourceware.org \
    --cc=keiths@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).