From: Keith Seitz <keiths@redhat.com>
To: insight <insight@sourceware.org>
Subject: Re: [PATCH] Use system Tcl et al
Date: Sat, 02 Aug 2008 23:46:00 -0000 [thread overview]
Message-ID: <4894F1BF.7000802@redhat.com> (raw)
In-Reply-To: <4894DE8F.4090306@redhat.com>
Just a quick follow-up...
Keith Seitz wrote:
> 2) I have not tested cygwin a lot [and mingw at all]. I hope to
> investigate this more fully now that the initial support is in. You
> *must* use in-tree Tcl/Tk/Itcl for Cygwin, since the 3.2 package of Itcl
> that is distributed with Cygwin does not support the Tcl Extension
> Architecture.
I tried in-tree tcl/tk/itcl with Cygwin. With the libgui patch I just
committed, this should now work.
> 4) I haven't tried the testsuite yet. [I know, that's bad. Probably very
> bad, but I'll address that in time.]
Using system tcl/tk/itcl/itk/iwidgets, I can run the testsuite. It has
38 failures (most in c[pp]_variable.exp).
That's all for now.
Keith
next prev parent reply other threads:[~2008-08-02 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 22:25 Keith Seitz
2008-08-02 23:46 ` Keith Seitz [this message]
2008-08-03 14:06 ` Tom Tromey
2008-08-03 17:41 ` Keith Seitz
2008-08-03 20:59 ` Tom Tromey
2008-08-03 21:51 ` 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=4894F1BF.7000802@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
/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).