X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Rugxulo Newsgroups: comp.os.msdos.djgpp Subject: Re: gcc difficulties on MSDOS 6.22 with LFN driver installed Date: Wed, 31 Aug 2011 12:37:57 -0700 (PDT) Organization: http://groups.google.com Lines: 44 Message-ID: <28198a6d-3543-430d-8d2b-e0ba3b46a552@gz5g2000vbb.googlegroups.com> References: <201108310027 DOT 22056 DOT juan DOT guerrero AT gmx DOT de> <201108312117 DOT 54522 DOT juan DOT guerrero AT gmx DOT de> NNTP-Posting-Host: 65.13.115.246 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: posting.google.com 1314819477 8145 127.0.0.1 (31 Aug 2011 19:37:57 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: Wed, 31 Aug 2011 19:37:57 +0000 (UTC) Complaints-To: groups-abuse AT google DOT com Injection-Info: gz5g2000vbb.googlegroups.com; posting-host=65.13.115.246; posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HUALESNKRC X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20100101 Firefox/6.0,gzip(gfe) Bytes: 3022 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p7VJj2aU009019 Reply-To: djgpp AT delorie DOT com Hi, On Aug 31, 2:17 pm, Juan Manuel Guerrero wrote: > Am Mittwoch, 31. August 2011 schrieb Eli Zaretskii: > > > > From: Juan Manuel Guerrero > > > Date: Wed, 31 Aug 2011 00:27:21 +0200 > > > > cc1.exe: c:/djgpp-2.04/bin/../lib/gcc/djgpp/3.44/djgpp.ver: Value too large (EOVERFLOW) > > > 1.c:1:19: c:/djgpp-2.04/include/stdio.h: Value too large (EOVERFLOW) > > > Can you find out where did this error message come from?  Which system > > call or library function emits EOVERFLOW? > > The functions generating EOVERFLOW are filelength() and lfilelength().  Both of > them usefunction  0x7A46 to get the file size if LFN support is available.  But I > assume that neither MSDOS nor DOSLFN  provide the required function.  May we > need to disind a better to certainly identify the OS used. I don't have easy access to MS-DOS 6.22 these days (old 486 is disconnected, too painful to setup right now, half dead anyways), but I vaguely remember seeing similar issues. You could try StarLFN instead, it should work, but no promises how well. In particular, I can't remember exactly, but you may or may not have to make the LONGNAME.DAT file not be +H (hidden), at least on FreeDOS, not sure about MS-DOS. (It also supports direct VFAT access a la DOSLFN, but I usually avoid that.) http://sta.c64.org/starlfn.html starlfn /i ... starlfn /u P.S. I didn't write it, obviously, but at one time I did get the crazy idea to rebuild it with JWasm for 8086, and esp. strip out all the (unneeded, patented) VFAT crud. Never got around to it, of course. Still would be worth doing, IMHO. (And it's not hard, just tedious.)