X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f NNTP-Posting-Date: Mon, 06 Nov 2006 12:51:28 -0600 Message-ID: <454F8223.EC4BCE91@yahoo.com> Date: Mon, 06 Nov 2006 13:42:43 -0500 From: CBFalconer Organization: Ched Research http://cbfalconer.home.att.net X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.os.msdos.djgpp Subject: Re: DJGPP 2.04 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 42 NNTP-Posting-Host: 216.195.149.19 X-Trace: sv3-ERFevyYcB94suruEMyeBXB8wfQ33m9vxPOMMVRMNgrs3C0E3KU07gRq8AynL/kcVHq5GDBk2fgngPz+!YqJrgPffVbh415aItPlfvgs1gAS+H4hRnCwClyFzENwQr8E+U4S5ME7MbvUpmw== X-Complaints-To: abuse AT gwi DOT net X-DMCA-Complaints-To: abuse AT gwi DOT net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.32 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Gordon DOT Schumacher AT seagate DOT com wrote: > "Gerrit van Niekerk" wrote >> On 4 Nov 2006 at 14:35, Florian Xaver wrote: > >>> I am using the inofficial "2.04" version, would it be much work >>> to make it official? I haved had never problems. It would maybe >>> bring new life into DJGPP... >>> >> This issue comes up from time to time. Some of the problems to be >> sorted out: >> >> http://homepages.nildram.co.uk/~phekda/richdawe/djgpp/2.04/status204.html >> >> As I understand it, the real problem is that there is nobody >> willing/able to act as a release manager. Any volunteers? > > I can't step forward right at the immediate moment, because I'm > beyond up to my eyeballs in trying to get the software I work on > released for my organization. > > But my department (in both its current incarnation and in its > previous one at Maxtor) have both made great use of DJGPP over the > last few years, and once I get things a little more stabilized, > I'd like to step forward to do that. I've had initial discussions > on the topic with my boss and he gave an initial okay, once this > big push is past. Glad to hear it. Please look closely at the problems with the existing malloc package, and my replacement nmalloc. One of the problems is exposed by the evilalgo.c test. My health prevents me from doing anything major at this point. But if things get moving I shall try to attack the memalign (non-standard) problem again. At one point I understood this was needed to handle the later gcc versions. -- Chuck F (cbfalconer at maineline dot net) Available for consulting/temporary embedded and systems.