public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@cygnus.com>
To: Insight Maling List <insight@sources.redhat.com>
Subject: [PATCH] Absolute pathname patch (again)
Date: Thu, 16 Aug 2001 16:04:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0108161600010.10383-100000@makita.cygnus.com> (raw)

Hi,

Well, it turns out that my little tweak this morning was a good start, but
still insufficient. You could run insight from the gdb/ directory and
install directory quite reliably. But you could not run the testsuites or
run it from another working directory, i.e., gdb/gdb. Sigh.

This patch should pretty much fix this once and for all. (I hope. ;-)
Keith

ChangeLog
2001-08-16  Keith Seitz  <keiths@redhat.com>

	* generic/gdbtk.c (gdbtk_init): Revert change from earlier.
	It is insufficient. We must get the absolute pathname
	from autoconf.
	Don't bother setting TCL_LIBRARY: it must be set already
	in order for us to execute a script.

Patch
Index: generic/gdbtk.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk.c,v
retrieving revision 1.17
diff -u -p -r1.17 gdbtk.c
--- gdbtk.c	2001/08/16 17:38:18	1.17
+++ gdbtk.c	2001/08/16 23:03:51
@@ -410,14 +410,6 @@ gdbtk_init (argv0)

       static char set_libs_path_script[] = "\
 	  set srcDir [file dirname [file dirname $env(TCL_LIBRARY)]];\n\
-          set cwd [pwd]\n\
-          cd $srcDir\n\
-          set srcDir [pwd]\n\
-          cd $cwd\n\
-\
-	  if {![info exists env(TCL_LIBRARY)]} {\n\
-	      set env(TCL_LIBRARY) [file join $srcDir tcl library]\n\
-	  }\n\
 \
 	  if {![info exists env(TK_LIBRARY)]} {\n\
 	      set env(TK_LIBRARY) [file join $srcDir tk library]\n\

                 reply	other threads:[~2001-08-16 16:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.GSO.4.33.0108161600010.10383-100000@makita.cygnus.com \
    --to=keiths@cygnus.com \
    --cc=insight@sources.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).