public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Jerzy Witkowski <jwi@pl.ibm.com>,
	"insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: cygwin Tcl/Tk 20030214-1: [incr Tcl/Tk] interpreters missing
Date: Fri, 21 Mar 2003 17:11:00 -0000	[thread overview]
Message-ID: <20030321160545.GB18828@redhat.com> (raw)
In-Reply-To: <1048261257.1492.4.camel@lindt.uglyboxes.com>

On Fri, Mar 21, 2003 at 07:40:57AM -0800, Keith Seitz wrote:
>On Fri, 2003-03-21 at 04:39, Jerzy Witkowski wrote:
>> I refreshed my Cygwin installation and found out that [incr Tcl/Tk]
>> interpreters are missing. In the previous version Tcl/Tk interpreters were
>> named `cygtclsh80.exe', `cygwish80.exe', `cygitclsh30.exe' and
>> `cygitkwish30.exe'.
>
>I suggest you go to the official Tcl project pages and read up on Tcl
>8.4 and, especially "TEA", the Tcl Extension Architecture. There will
>never again be an Incr Tcl shell: it's not needed.
>
>To get an Itcl shell, you must configure the build with
>"--enable-shared" (on unix only -- cygwin always builds this way). When
>you start tclsh, give it the command "package require Itcl". This will
>load the Itcl extension. POOF! You know have an itclsh.exe. Do the same
>with wish, and you have an itkwish.exe.

That doesn't seem to work too well on cygwin:

couldn't load library "F:/cygwin/lib/itcl3.2/../libitcl32.a": invalid argument

cgf

  reply	other threads:[~2003-03-21 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 15:32 Cygwin " Jerzy Witkowski
2003-03-21 15:39 ` Keith Seitz
2003-03-21 17:11   ` Christopher Faylor [this message]
2003-03-24 10:33     ` cygwin " Keith Seitz
2003-09-24 10:51 Jerzy Witkowski

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=20030321160545.GB18828@redhat.com \
    --to=cgf@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=jwi@pl.ibm.com \
    --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).