From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: insight@sourceware.org
Subject: Re: Next Release Status
Date: Wed, 09 Nov 2011 00:17:00 -0000 [thread overview]
Message-ID: <20111109001650.GA778@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4EB9A9CE.3030902@gmx.de>
On Tue, Nov 08, 2011 at 11:14:38PM +0100, Matthias Andree wrote:
>Am 08.11.2011 18:50, schrieb Keith Seitz:
>> Hi,
>>
>> Given some demand, I am planning on doing an official release of Insight
>> sometime just after the GDB 7.4 release (process starting soon).
>>
>> My primary goals for this release (largely just an update/bugfixes) are
>> that it build/work on Linux (my platform), MinGW, and Cygwin.
>>
>> I spent some time this weekend rummaging around the sources attempting
>> to get this stuff working. Here's a little status report on my progress.
>>
>> Linux: builds and runs okay. Found a memory corruption bug in the
>> register window (affects all hosts). Needs to be fixed before release.
>>
>> MinGW: Had patches lying around to get build working, but I forgot. So I
>> re-invented the wheel. No big deal. I will check these in. There is,
>> however, a startup problem with libgui on this platform. It complains
>> about being unable to find pkgIndex.tcl. Hopefully, not too painful to fix.
>>
>> Cygwin: This is the nightmare. Tcl et al are completely broken. Instead
>> of using my ancient Windows 2000 box, I have installed a VM on my linux
>> box and put a modern Windows installation in there. Now I see all the
>> problems that people have reported throughout the years that I could
>> never reproduce! Example: conflicts with winsock & Cygwin's posix layer.
>> Ouch. Currently, this is the only platform for which I do not have a
>> working build.
>
>That's been the status quo ever since Cygwin 1.7.0 got released.
Actually, I've been able to build this without much effort. I just
don't like the current state of affairs wrt cygwin tcl/tk and insight so
I haven't been motivated to make a release.
>> I hope over the next few weeks, leading up to the GDB 7.4 release, to
>> get these problems resolved. If you'd like to help (especially with
>> Cygwin!), please let me know.
>>
>> If anyone has any other peeves or important bugs, please also let me
>> know, and I will try to address them before this next release.
>
>My idea is to contact the Cygwin mailing list (which is read by the
>maintainers). Tell them your plans and ask for help with Tcl/Tk. I
>suppose you'll hear "sorry, no maintainer" though. And tell them that
>you need Tcl/Tk with POSIX-style networking.
There's no need to do this. The maintainer reads this list.
cgf
next prev parent reply other threads:[~2011-11-09 0:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 17:51 Keith Seitz
2011-11-08 22:14 ` Matthias Andree
2011-11-09 0:17 ` Christopher Faylor [this message]
2011-11-09 23:32 ` Keith Seitz
2011-12-15 14:22 Bahadir Balban
2011-12-15 14:38 ` Bahadir Balban
2011-12-17 18:17 ` Keith Seitz
2011-12-18 18:37 ` Bahadir Balban
2011-12-19 17:41 ` Keith Seitz
2011-12-20 12:18 ` Bahadir Balban
2011-12-17 18:14 ` 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=20111109001650.GA778@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--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).