From: Gene Smith <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: Re: 20090609-cvs bad on linux (build fail cygwin)
Date: Tue, 07 Jul 2009 03:29:00 -0000 [thread overview]
Message-ID: <h2ufer$s76$1@ger.gmane.org> (raw)
In-Reply-To: <h2uf09$rg4$1@ger.gmane.org>
(The last two exchanges never got to the list, I just added them.
-gene )
Gene Smith wrote:
> I think winavr project distributes a mingw build of insight. I am >
>pretty sure mingw has no "system" tcl/tk. However, I don't think many
>(or any?) winavr or users use it.
I didn't know that... Yeah, I suspect Tcl/Tk will just stay in
sourceware for a while. Red Hat still uses it, too, I think.
> But since you didn't tell me how to select "system" tcl/tk vs.
>built-in I assume you don't think that is related to my problem.
Sorry -- I missed that. To build using the system-supplied tcl/tk, make
sure you have the dev packages (on linux) installed: tcl-devel,
tk-devel, itcl-devel, itk-devel. Remove (or rename) tcl, tk, and itcl
from your source directory, and the build will find the system-installed
versions. [I don't recall if this is absolutely necessary, but I do it
anyway.]
When starting an untested build configuration for the first time, I
usually do a "make configure-gdb" and check the output of configure that
it found the tcl/tk/itcl/itk stuff that I expected it to.
Keith
prev parent reply other threads:[~2009-07-07 3:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 19:04 Gene Smith
2009-06-12 17:28 ` Keith Seitz
2009-06-12 22:04 ` Gene Smith
2009-06-12 23:38 ` Gene Smith
2009-06-16 18:01 ` Gene Smith
2009-06-16 18:40 ` Keith Seitz
2009-06-16 18:48 ` Gene Smith
2009-06-16 18:53 ` Keith Seitz
2009-07-07 3:22 ` Gene Smith
2009-07-07 3:29 ` Gene Smith [this message]
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='h2ufer$s76$1@ger.gmane.org' \
--to=gds@chartertn.net \
--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).