X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient: djgpp-workers AT delorie DOT com
Message-ID: <49E55BBB.4060403@iki.fi>
Date: Wed, 15 Apr 2009 06:59:55 +0300
From: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent: Thunderbird 2.0.0.21 (X11/20090320)
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: Resurrecting GDB for version 7.0 release
References: <83fxgbm0oa DOT fsf AT gnu DOT org>
In-Reply-To: <83fxgbm0oa.fsf@gnu.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Eli Zaretskii kirjoitti:
> The last version of GDB ported to DJGPP was 6.1.  That was 5 years
> ago.
> 
> GDB 7.0 is slated for release in early June this year, and I thought
> it would be a good idea to resurrect the DJGPP port in time for that.
> With that in mind, I set out to build the current CVS code base, debug
> whatever problems I find, and start using it in my occasional DJGPP
> related work.
> 
> I'm now past the initial configury and compilation problems, and
> beginning to work on the problems I find as I go.  (People who want
> details can track my progress by reading my messages posted to the
> gdb-patches AT sourceware DOT org mailing list.)
> 
> GDB 7.0 will support Python scripting, a powerful new feature.  To get
> that working with DJGPP, I need a working port of libpython.  The only
> DOS port of Python I could find was built with DJGPP v2.04, so it is
> incompatible with what I use (v2.03).  On top of that, there's no
> libpython.a in that port, only the binary of the Python interpreter.

Some time ago I built gdb-6.8 with DJGPP v2.04, but failed to do that
with v2.03r2. I do not remember details now.

Andris