From: Keith Seitz <keiths@redhat.com>
To: Pavel Roskin <proski@gnu.org>
Cc: insight@sourceware.org
Subject: Re: New release?
Date: Thu, 02 Feb 2006 03:23:00 -0000 [thread overview]
Message-ID: <43E17B06.7050404@redhat.com> (raw)
In-Reply-To: <1138843155.17621.10.camel@dv>
Pavel Roskin wrote:
> I'm surprised that there have been no releases since December, although
> 6.4.0 has a known build problem (tcl/unix/configure: line 7061: syntax
> error) with a known fix.
GDB 6.4.1 has not been released. Insight releases are tied to GDB
releases (mainly for my own convenience -- since I don't really do a
whole lot with insight any more).
> Possible fixes, sorted by impact:
>
> Remove tcl/tk from the sources
> Update tcl/tk to the latest versions
Patches are always welcome. This first item is high on my hit list, but
I haven't had the time for a long, long time, but one of these days,
I'll get fed up and do it. Truth be told, I don't really think it would
take me more than about 10-15 hours, including testing.
> Fix stray quotes in the currently bundled tcl/tk sources
>
> For the latest approach, the patch is attached.
Yes, I will check and apply your patches. Thank you.
Keith
prev parent reply other threads:[~2006-02-02 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 1:19 Pavel Roskin
2006-02-02 3:23 ` Keith Seitz [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=43E17B06.7050404@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=proski@gnu.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).