X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: "decker" <bdeck AT lycos DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: DJGPP Modifications
Date: 12 May 2006 03:56:25 -0700
Organization: http://groups.google.com
Lines: 37
Message-ID: <1147431385.580249.141860@i39g2000cwa.googlegroups.com>
NNTP-Posting-Host: 220.233.177.46
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1147431390 9477 127.0.0.1 (12 May 2006 10:56:30 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: Fri, 12 May 2006 10:56:30 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse AT google DOT com
Injection-Info: i39g2000cwa.googlegroups.com; posting-host=220.233.177.46;
   posting-account=R02xJAwAAAASwE3U1qQ37KcHXmocYA_U
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hello.


First, I received, in part, the following email from D Borca:

> I've uploaded a new version of DJGPP ELF on my page:
> http://www.geocities.com/dborca/djgpp/elf/djelf.html
>
> The binaries are on another geocities page, so you may
> experience geocities' bandwidth limit.
>
> This version fixes a few bugs, has complete libgcc,
> libm and libc (all are provided as shared and static)
> and more important, brings on the C++ compiler and
> libraries.

I made thefollowing remark on #djgpp, for what it is worth...

> DJGPP should consider 'merging' the watt-32 BSD-libsocket include files into the core
> reason being that there are a few incompatibilities (like sys/cdefs.h) that need to be done by
> hand to 'integrate' watt-32 correctly as a 'libsocket' into DJGPP.
> I am currently doing this, but long-term I think that the LAST thing that the remaining DJGPP
> developers need are TWO distro to deal with.
> They should also consider Daniel Borca's djgpp-elf patches ASAP.
> There is too much good porting-base functionality there to ignore, and if they don't take it, it
> WILL RESULT IN TWO DISTROS (YUCK!)

Basically, DXE3 will no longer be developed. PythonD is an example of a
project which has always been 'built on DJGPP', so the solution of
forking is not very desirable to me.

But that is the point we are coming to.

Thanks,
Ben Decker
caddit.net