delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2006/06/10/01:16:48

X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
Message-ID: <448A2BDA.DE2DC7E0@yahoo.com>
Date: Fri, 09 Jun 2006 22:18:02 -0400
From: CBFalconer <cbfalconer AT yahoo DOT com>
Organization: Ched Research http://cbfalconer.home.att.net
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: 2.04 release
References: <1713 DOT 220 DOT 233 DOT 177 DOT 46 DOT 1149833809 DOT squirrel AT cafemail DOT mcadcafe DOT com> <4489A2DE DOT 7050203 AT iki DOT fi>
Reply-To: djgpp-workers AT delorie DOT com

Andris Pavenis wrote:> 
> decker AT dacafe DOT com kirjoitti:
>>
>>>> I am trying to understand the issues that are preventing DJGPP
>>>> 2.04 from release.
>>>
>>> See
>>> http://homepages.nildram.co.uk/~phekda/richdawe/djgpp/2.04/status204.html
>>>
>>> There's a list of issues there.
>>
>> First, sorry about any previous "posts" of mine that didn't make
>> sense :(
>>
>> I am wondering why the 2.04 status page is being maintained on
>> the site of someone no longer active with the project.
>>
>> Who is the 2.04 release manager at this point in time?
>>
>> Which of the issues listed on aforementioned website are truly
>> holding 2.04 release back? Priority 1, 2, or all of them (because
>> I doubt at this rate that you will ever get them *all* fixed).
>>
>> The 2.04 support pages should definitely be moved to someone
>> active with the project. The current situation *appears*
>> pretty dead actually.
> 
> Well. I see also very little activity on my webpage, where I put
> archives of GCC-4.1.1 for DJGPP. Most feedback is about GCC-4.1.1
> Linux-to-DJGPP cross-compiler RPMs, which are also there. Don't
> not have enough however ask me to put DJGPP v2.04 status page
> there as I will time for maintaining it.
> 
> I think, that it's really a time simply to throw what we have at
> the users and release it as 2.04. I'm afraid, that otherwise it
> will never be done. Of course also DJGPP v2.04 does not build
> with current GCC, so one must use gcc-3.3.6 or maybe gcc-3.4.4.
> Current version is of course not ideal, but I don't believe that
> we ever have better unless it will be released.

I wish it would go out including my nmalloc.  Although I never got
the memalign stuff into it, I am quite proud of the package and the
built in debugging capability.  I believe someone was running it
for some time, and found no problems.  The only reason, I believe,
for the memalign stuff was to work with gcc, and that seems to
already be problematical.  I don't think it is smart to have gcc
dependant on such non-standard things.

-- 
 "Our enemies are innovative and resourceful, and so are we. 
  They never stop thinking about new ways to harm our country
  and our people, and neither do we."          -- G. W. Bush.
 "The people can always be brought to the bidding of the
  leaders.  All you have to do is tell them they are being
  attacked and denounce the pacifists for lack of patriotism
  and exposing the country to danger. It works the same way
  in any country."                         --Hermann Goering.



- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019