X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=BO6J2uD3OccEK36RjLfxG8KzXfofdAOUU0AcVxvTK8M=; b=S0cMLh5niJObohnSKI50HHOQtVOxd6ilamxJS7zFe+XpFlJm6Z77gnBLZSIgVrvrs4 CPopnipbi1ZZD+pxRAXXxsGSo8TGEhAzMzF2ITcQATpDiUYtxUM4QoO/+FRpoP/zaqIY 4tJo+xGvTUhllooKyn3F7xEbFIzuPRdTk/s2k= MIME-Version: 1.0 In-Reply-To: <83zkincty6.fsf@gnu.org> References: <201108310027 DOT 22056 DOT juan DOT guerrero AT gmx DOT de> <201108312117 DOT 54522 DOT juan DOT guerrero AT gmx DOT de> <038ae4ff-44f2-4ad2-b806-a6ed9b6085a2 AT o9g2000vbo DOT googlegroups DOT com> <83zkincty6 DOT fsf AT gnu DOT org> Date: Fri, 2 Sep 2011 11:07:28 +0300 Message-ID: Subject: Re: gcc difficulties on MSDOS 6.22 with LFN driver installed From: Ozkan Sezer To: djgpp AT delorie DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p8287WIJ019759 Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Fri, Sep 2, 2011 at 9:57 AM, Eli Zaretskii wrote: >> From: Juan Manuel Guerrero >> Date: Thu, 1 Sep 2011 15:19:03 -0700 (PDT) >> >> OFYI, I have djgpp 2.03 installed on the same partition with the same >> MSDOS 6.22 so I can choose if I want to compile with 2.04 or 2.03. >> gcc 4.6.1 and djgpp-2.03 work flawlessly. > > Wait a minute.  Are you saying that the problem is _only_ with GCC > compiled with DJGPP 2.04, and that 2.03-compiled GCC works?  I don't > think you said that before. > > If you compile with v2.03 a simple program that calls 7A46, and then > run it with DOSLFN, does it also fail? > > If so, this is certainly due to the use of 7A46, because in v2.03 > `filelength' didn't call that function and `lfilelength' didn't exist AFAICS, filelength() calls 71A6, not 7A46. (Typo?) OTOH, filelength() from 2.03 didn't call 71A6 either. > at all. > > So I think we need to fix these 2 functions to work around this > problem. >