X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient:	djgpp-workers AT delorie DOT com
Date:	Wed, 15 Apr 2009 11:10:30 +0300
From:	Eli Zaretskii <eliz AT gnu DOT org>
Subject:	Re: Resurrecting GDB for version 7.0 release
In-reply-to:	<49E55BBB.4060403@iki.fi>
X-012-Sender:	halo1 AT inter DOT net DOT il
To:	djgpp-workers AT delorie DOT com
Message-id:	<838wm2mj61.fsf@gnu.org>
References:	<83fxgbm0oa DOT fsf AT gnu DOT org> <49E55BBB DOT 4060403 AT iki DOT fi>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Date: Wed, 15 Apr 2009 06:59:55 +0300
> From: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
> 
> 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.

Thanks for the data point.  As I said, I'm past the initial build
problems, and I'm using the latest djdev203.zip, from August 2002.
The build problems I had were all solved by upgrading Bash and other
packages, like Fileutils and Sh-utils, to the latest ports, but still
based on v2.03 (i.e. from current/v2gnu/, not from beta/v2gnu/).  So
whatever problems you had are either something specific to your setup,
or do not exist anymore in the current GDB CVS.

I did encounter real problems during the build, though, and I will
announce here when all the solutions for them are in GDB CVS, at which
time I'd be grateful if you and others could try building a snapshot
to see if that works for someone other than myself.

I'm using v2.03 because it is well tested and very stable.  Over the
time, I replaced only 3 functions in it with versions based on the
current CVS: `rename', `delay' and `utime', because the original v2.03
versions did not work on my Windows XP machine, where I do all the
DJGPP-related work these days (I no longer have access to pure DOS
machines).  I don't envision myself switching to v2.04 in the
foreseeable future, because when I encounter a problem, I want to know
that the library is the last suspect, not the first, and v2.03 so far
proved that this principle holds water for it.  With so little time I
can invest to DJGPP-related work, I simply cannot afford wasting my
time on bugs in the library instead of debugging the application code.

In any case, the main help I need from people here is with porting
libpython and libexpat.  All the other problems I've discovered until
now where minor and easy to track down and solve.

Thanks.

- Raw text -