X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Fri, 14 Feb 2020 18:53:34 +0100
Message-ID: <8736bdf42p.wl-tomas@basun.net>
From: Tomas By <tomas AT basun DOT net>
To: djgpp AT delorie DOT com
Subject: Re: Emacs 26 / FreeDOS
In-Reply-To: <83imk9pmxx.fsf@gnu.org>
References: <87imkakuab DOT wl-tomas AT basun DOT net>
	<83wo8ppppd DOT fsf AT gnu DOT org>
	<8736bdh8vw DOT wl-tomas AT basun DOT net>
	<83imk9pmxx DOT fsf AT gnu DOT org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue)
 FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/25.2
 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-bounce-key: webpack.hosteurope.de;tomas AT basun DOT net;1581702841;9c2f6626;
X-HE-SMSGID: 1j2f9k-0006yL-1g
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, 14 Feb 2020 09:55:54 +0100, Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com] wrote:
> 
> > Date: Fri, 14 Feb 2020 09:26:43 +0100
> > From: Tomas By <tomas AT basun DOT net>
> > 
> > I have noticed some file name shenanigans between Linux and Freedos:
> > the machine is dual book (triple even) and I unzipped a file from
> > Linux onto the Freedos FAT32 disk (not the DJGPP stuff), [...]
> [...]
> 
> Why not unzip the files from FreeDOS instead?  That would at least
> ensure that the OS on which you run Emacs can access the files and
> directories.


To clarify this point...

I used "unzip32" in FreeDOS to unzip all the DJGPP files.

I then tried to unzip the sources of the Freeimage library (7.4 MB) on
the FreeDOS disk but got an error about broken zip file. I am not
currently able to reproduce this. When I try to do the same as what I
believe is what I did earlier, it just says file not found.

However, with the files unzipped from Linux, I was able to start
compiling the library. This worked for some hours, and then it failed
with a C error (not file name stuff).

So there may be some remote connection between this and the Emacs
problem in that the underlying causes, at some degree of separation,
are the same.

/Tomas