From: "Martin M. Hunt" <hunt@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Ben Elliston <bje@wasabisystems.com>,
"insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: building Tk from the src tree
Date: Mon, 13 Oct 2003 20:26:00 -0000 [thread overview]
Message-ID: <1066076774.2345.11.camel@dragon> (raw)
In-Reply-To: <1066059763.1675.3.camel@lindt.uglyboxes.com>
On Mon, 2003-10-13 at 08:42, Keith Seitz wrote:
> On Sun, 2003-10-12 at 23:20, Ben Elliston wrote:
> > I'm trying to build Tcl/Tk from the src tree on a Cygwin system that
> > has no previous installation of Tcl/Tk. I'm striking a problem
> > whereby tk/win/configure invokes SC_PROG_TCLSH to find a tclsh shell
> > for building purposes -- it searches the user's $PATH and the build
> > tree for tclsh, but the tcl build directory will have only been
> > configured, not built. How is this meant to work?
> >
>
> I just noticed this myself. Since we now use the same configury as the
> standard Tcl and Tk (the installation dir tweak aside), I would say this
> is a problem with Tk configury upstream.
Actually we don't really use the same configury. Importing tcl/tk 8.4.1
and getting Insight to use it was trivial. But I spent days on
configury stuff trying to get it to work in our framework. It wouldn't
surprise me at all to find there were lots of errors in it.
--
Martin M. Hunt <hunt@redhat.com>
Red Hat Inc.
next prev parent reply other threads:[~2003-10-13 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 6:20 Ben Elliston
2003-10-13 15:39 ` Keith Seitz
2003-10-13 20:26 ` Martin M. Hunt [this message]
2003-10-14 11:24 ` Ben Elliston
2003-10-14 16:27 ` Keith Seitz
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=1066076774.2345.11.camel@dragon \
--to=hunt@redhat.com \
--cc=bje@wasabisystems.com \
--cc=insight@sources.redhat.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).