From: Keith Seitz <keiths@cygnus.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Syd Polk <jazzman@bayarea.net>,
Insight List <insight@sourceware.cygnus.com>
Subject: Re: regenerating tclIndex
Date: Tue, 02 Oct 2001 15:51:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0111190844550.16197-100000@makita.cygnus.com> (raw)
In-Reply-To: <87itc72qi5.fsf@creche.redhat.com>
On 19 Nov 2001, Tom Tromey wrote:
> Syd> Run "make" from the source directory. Make sure tclsh is installed.
>
> That doesn't work.
> The current gdbtk/library/Makefile still references itclsh3.0.
Doh. My bad? Didn't we decide that we would just require developers to
have tclsh8.3?
So we could do something like:
Index: Makefile
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/Makefile,v
retrieving revision 1.2
diff -u -p -r1.2 Makefile
--- Makefile 2001/01/03 05:34:04 1.2
+++ Makefile 2001/11/19 16:45:23
@@ -1,10 +1,10 @@
TCL := $(wildcard *.tcl *.itcl *.ith *.itb)
-ITCL_SH = itclsh3.0
+TCLSH = tclsh8.3
tclIndex: $(TCL) Makefile
- echo "auto_mkindex `pwd` $(TCL)" | $(ITCL_SH)
+ echo "package require Itcl 3.0; auto_mkindex `pwd` $(TCL)" | $(TCLSH)
tags: TAGS
TAGS: $(TCL)
WARNING: multiple messages have this Message-ID
From: Keith Seitz <keiths@cygnus.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Syd Polk <jazzman@bayarea.net>,
Insight List <insight@sourceware.cygnus.com>
Subject: Re: regenerating tclIndex
Date: Mon, 19 Nov 2001 08:46:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0111190844550.16197-100000@makita.cygnus.com> (raw)
Message-ID: <20011119084600.16N9VendRNgRI6kIawTYCZz6hB7A_POwjGWMTGp7VDA@z> (raw)
In-Reply-To: <87itc72qi5.fsf@creche.redhat.com>
On 19 Nov 2001, Tom Tromey wrote:
> Syd> Run "make" from the source directory. Make sure tclsh is installed.
>
> That doesn't work.
> The current gdbtk/library/Makefile still references itclsh3.0.
Doh. My bad? Didn't we decide that we would just require developers to
have tclsh8.3?
So we could do something like:
Index: Makefile
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/Makefile,v
retrieving revision 1.2
diff -u -p -r1.2 Makefile
--- Makefile 2001/01/03 05:34:04 1.2
+++ Makefile 2001/11/19 16:45:23
@@ -1,10 +1,10 @@
TCL := $(wildcard *.tcl *.itcl *.ith *.itb)
-ITCL_SH = itclsh3.0
+TCLSH = tclsh8.3
tclIndex: $(TCL) Makefile
- echo "auto_mkindex `pwd` $(TCL)" | $(ITCL_SH)
+ echo "package require Itcl 3.0; auto_mkindex `pwd` $(TCL)" | $(TCLSH)
tags: TAGS
TAGS: $(TCL)
next prev parent reply other threads:[~2001-11-19 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 14:55 Syd Polk
2001-10-02 14:55 ` Tom Tromey
2001-10-02 15:51 ` Keith Seitz [this message]
2001-10-03 9:39 ` Tom Tromey
2001-11-19 12:25 ` Tom Tromey
2001-11-19 8:46 ` Keith Seitz
2001-11-18 22:36 ` Tom Tromey
2001-11-18 21:32 ` Syd Polk
[not found] <1006196231.29860.ezmlm@sources.redhat.com>
2001-10-02 16:09 ` Jim Ingham
2001-11-19 11:26 ` Jim Ingham
-- strict thread matches above, loose matches on Subject: below --
2001-10-02 14:41 Tom Tromey
2001-11-18 18:02 ` Tom Tromey
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.0111190844550.16197-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=jazzman@bayarea.net \
--cc=tromey@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).