public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Ian Roxborough <irox@evilpeople.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: keiths@cygnus.com, insight@sources.redhat.com
Subject: Re: Tcl/Tk 8.3 upgrade...
Date: Thu, 14 Jun 2001 20:03:00 -0000	[thread overview]
Message-ID: <20010614200332.435367f8.irox@evilpeople.com> (raw)
In-Reply-To: <3B293F80.2CF6F0D6@cygnus.com>

On Thu, 14 Jun 2001 18:49:36 -0400
Fernando Nasser <fnasser@cygnus.com> wrote:
> Yes, we must run Insight from the build directory.

And that wouldn't be an issue.  It would still run, just
a script (put in the build directory at make or configure
time) would set some environment variables and run gdb.

> Also, how would this affect testsuite runs?

This shouldn't affect the testsuites. They run fine.
 
> Note that if we make insight's own main.c we can add some code
> to handle these situations.

Yeah, I see that.  We can make this set TCL_LIBRARY, etc. before
it tries any *_inits and everything should work.

Ian.
-- 
What would Jenna Bush do?

  reply	other threads:[~2001-06-14 20:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 13:11 Ian Roxborough
2001-06-12 18:18 ` Keith Seitz
2001-06-12 22:11   ` Ian Roxborough
2001-06-13  8:08   ` Andrew Cagney
2001-06-13  8:12     ` Keith Seitz
2001-06-13 13:06   ` Mo DeJong
2001-06-14  1:30   ` Ian Roxborough
2001-06-14  8:27     ` Keith Seitz
2001-06-14 15:30       ` Ian Roxborough
2001-06-14 15:33         ` Keith Seitz
2001-06-14 15:49           ` Fernando Nasser
2001-06-14 20:03             ` Ian Roxborough [this message]
2001-06-15  6:35               ` Fernando Nasser
2001-06-15 10:59                 ` Ian Roxborough
2001-06-15 11:14                   ` Keith Seitz
2001-06-14 20:17           ` Ian Roxborough
2001-06-14 17:18         ` Mo DeJong

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=20010614200332.435367f8.irox@evilpeople.com \
    --to=irox@evilpeople.com \
    --cc=fnasser@cygnus.com \
    --cc=insight@sources.redhat.com \
    --cc=keiths@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).