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:22:00 -0000 [thread overview]
Message-ID: <h2uf09$rg4$1@ger.gmane.org> (raw)
In-Reply-To: <4A37E8E9.7010406@redhat.com>
Keith Seitz wrote:
> Gene Smith wrote:
>> But I thought insight has it *own* gdb that never changes? Anyhow,
>> here are the step I use to build it:
>
> No, it does not. Insight CVS uses gdb CVS. Insight 6.8 uses gdb 6.8.
> It has its own versions of tcl, tk, itcl, etc, but those are now just
> copies of some release (currently 8.4, I think). Except on cygwin, I > do
> not use the supplied versions of tcl et al anymore. I use the
> system-supplied versions on Fedora.
>
> Kevin Buettner is working on updating tcl et al CVS on sourceware to
> the latest release.
>
>> Hopefully, this will help.
>
> I will give this a go by the end of the week.
>
>> P/S: I am still a bit confused as to whether I should be using the
>> "system" supplied tcl/tk or the tcl/tck code from insight. I think I
>> am using insight's. If I should use the system tcl/tk, how do I do
>> that?
>
> You can use whatever version you would like to. It has been a goal
> ofmine (for quite some time sadly) to eliminate our dependence on a
> sourceware-supplied tcl/tk/itcl. That requirement originally came in
> the days of Tcl 8.1, when we carried a bunch of local patches to Tcl.
> We didn't upgrade sourceware Tcl until 8.4 (or was it 8.3?) and our
> supplied version of Tcl became identical to upstream.
>
> A little while ago, I got around to eliminating the requirement for
> sourceware-supplied Tcl. But it remains for historical reasons (and
> because cygwin still requires it). If we got cygwin "fixed", I guess
> we could just simply eliminate it altogether from the repo if no other
> project was using it.
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.
>
> Keith
Thanks for explaining all this! Now I see.
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.
next prev parent reply other threads:[~2009-07-07 3:22 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 [this message]
2009-07-07 3:29 ` Gene Smith
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='h2uf09$rg4$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).