Message-ID: From: "Andris Pavenis" To: Eli Zaretskii Date: Fri, 30 Apr 1999 14:02:35 +0300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: v2.03: wrapping up CC: djgpp-workers AT delorie DOT com References: In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.02b14) Reply-To: djgpp-workers AT delorie DOT com On 27 Apr 99, at 15:31, Eli Zaretskii wrote: > > On Tue, 27 Apr 1999, Andris Pavenis wrote: > > > I suggest following way of testing: > > grep sources to find where DJGPP_MINOR is used > > > > add > > #if defined(__DJGPP__) && !defined(__DJGPP_MINOR__) > > #error DJGPP_MINOR is not defined > > #endif > > before using this macro > > Many packages include their private headers which then include other > headers which then include standard headers. I cannot afford going > through all the Megabytes of ported packages and do this. Volunteers > are welcome to do it, as always. > I had CD where I burned most v2* packages in November 8 (except some old ones and unfortunatelly also emacs alpha version). I grepped sources and found not so many packages where DJGPP_MINOR where used (really only some). Of course I wrote shell script to do that (under Linux). Perhaps I'll download missing and new packages I don't have and repeat that (unfortunatelly our local DJGPP mirror is temporary killed due to lack of disk space so download speed is much lower: <5Kb/sec instead of >200Kb/s. As the result it will take some time). After that I can try to patch affected packages, build them and send patches if success. As I said there are not so many. Of course we still have packages that are not yet released. So I hope we could make this "developers nightmare" not so painfull. Andris