public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: James Ingham <jingham@cygnus.com>
To: <andy@ads187.rhbd.psu.edu>
Cc: insight@sourceware.cygnus.com
Subject: Re: insight
Date: Thu, 03 Feb 2000 18:53:00 -0000	[thread overview]
Message-ID: <14490.16332.54329.837409@leda.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10002031926050.20982-100000@ads187.rhbd.psu.edu>

Andy,

If you did install this in a common location, then you will probably
have to do something like install the package in a temporary location,
then write a script that traverses the /tmp/insight tree, and in
parallel the normal prefix tree, and removes all the files in the
latter that are also in the former.

If you still have the build tree around, you can do the first step with:

make install-gdb prefix=/tmp/insight

The problem with this is that if you had tcl8.0, tk8.0 or Itcl3.0.1
installed on your machine in the same prefix directory, then this will
blow away the old tcl libraries & executables, probably not what you
wanted.

You can do this, however, and then reinstall Tcl from Scriptics or
wherever.

In general, as others have pointed out, its probably better not to
install a new package in your standard install directory.  You can
generally configure the prefix to be some temporary location, install
there, and keep the build tree around, and then when you know you like
the new package, rerun the make install passing the prefix argument
for the permanent location.

Jim

 > two questions:
 > 
 > How do I start it?
 > 
 > How do I get it off my machine?  There's no uninstall target in the
 > makefile, and the install target installs hundreds of files... not exactly
 > easy to track them all down.
 > 
 > I feel that these are reasonable questions.  Any help you could offer
 > would be greatly appreciated.  Thank you!
 > 
 > Andrew Sampson
 > ads187@psu.edu
 > 
 > note - the email address in the "From:" field doesn't exist...
 >        my real address is ads187@psu.edu
 > 
 > 

-- 
++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++
Jim Ingham                                              jingham@redhat.com
Red Hat, Inc.                      

  parent reply	other threads:[~2000-02-03 18:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-03 16:42 insight andy
2000-02-03 16:46 ` insight Mo DeJong
2000-02-03 18:26   ` insight Brendan J Simon
2000-02-03 18:53 ` James Ingham [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-10  9:58 insight malaoba
2019-01-16 19:40 ` insight Keith Seitz
2019-01-17 10:55   ` insight Andrew Burgess
2004-01-07  5:17 insight Himansu Doshi
2004-01-21 14:51 ` insight Keith Seitz
2003-02-09  3:07 Insight vk
2003-02-10 13:14 ` Insight Fernando Nasser
2002-12-04  6:53 insight luberzz
2002-12-04  7:06 ` insight Keith Seitz
2000-03-28 20:50 insight Reed Kotler (Reed Kotler Systems Inc)
2000-03-28 20:54 ` insight Mo DeJong
2000-03-28 21:02 ` insight Andrew Cagney
2000-03-23  8:00 insight Michael J. Carmody
2000-02-09  0:13 Insight Olivier Saudan
2000-02-09 11:05 ` Insight James Ingham
2000-01-13 14:54 Insight Miller, Rob
2000-01-16 20:02 ` Insight Brendan J Simon

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=14490.16332.54329.837409@leda.cygnus.com \
    --to=jingham@cygnus.com \
    --cc=andy@ads187.rhbd.psu.edu \
    --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).