X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Authenticated: #27081556
X-Provags-ID: V01U2FsdGVkX1/KwbtwkRPKRbHJGRMhHLMrI08u82oYUHzVXkRZyL
	4toNw3tZKDVxW/
From: Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
To: Ozkan Sezer <sezeroz AT gmail DOT com>
Subject: Re: Isues concerning the INT 21 Windows95 - LONG FILENAME FUNCTIONS (0x71XX) implementation.
Date: Mon, 26 Sep 2011 22:14:14 +0200
User-Agent: KMail/1.9.10
Cc: djgpp AT delorie DOT com
References: <201109260029 DOT 41840 DOT juan DOT guerrero AT gmx DOT de> <CAA2C=vDwj5Ph_u-Y56FfeAAHW5PcwiLym32kM3BVzjbsMXHd_g AT mail DOT gmail DOT com>
In-Reply-To: <CAA2C=vDwj5Ph_u-Y56FfeAAHW5PcwiLym32kM3BVzjbsMXHd_g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201109262214.15129.juan.guerrero@gmx.de>
X-Y-GMX-Trusted: 0

Am Montag, 26. September 2011 schrieb Ozkan Sezer:
> On Mon, Sep 26, 2011 at 1:29 AM, Juan Manuel Guerrero
> <juan DOT guerrero AT gmx DOT de> wrote:
> > OFYI, I have produced a second version of the patch presented the last time.
> > This time the patch shall fix the same issues but for djdev 2.03.
> >
> > Suggestions, objections, comments are welcome.
> >
> > Regards,
> > Juan M. Guerrero
> >
> 
> When I first apply my v2.03 compilability patch (see here under the
> "build v2.03 tree using gcc3x and gcc4x" thread:
> http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp-workers/2011/09/17/11:39:42
> )
> ... then your patch doesn't apply, which makes it less useful because
> v2.03 tree is not compilable with the newish gcc.  I can wiggle it
> to apply of course, so thanks for taking time to do this.

Sorry for that, but my intention never was to support the fixing of djdev203
sources out-of-the-box.  The patch shows how I fixed those 2.03 files that I will
include in the next version of libsupp to replace the originals from the libc.a
version of djdev 2.03.  As you have noted, they are not a drop-in replacement
for the 2.03 repository branch that can no longer be compiled with current
compiler versions.


> On another note, is any versions of your changes going in
> any time soon?

As soon as I have finished my last fixes and if no one opposes nor finds more
issues I think it could be commited.  May be this will take a week more.


Regards,
Juan M. Guerrero