Date: Sun, 16 May 1999 13:36:41 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Richard Dawe <richdawe AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: DJGPP installer [Was: Script language for installer]
In-Reply-To: <373B4568.1A3F9D02@bigfoot.com>
Message-ID: <Pine.SUN.3.91.990516133622.26252H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 13 May 1999, Richard Dawe wrote:

> I found a way around the problem of LFN vs. SFNs with libsocket by having
> Makefile targets that rename all the LFNs to SFNs.

Please tell more how does this solve the problem.

Also, beware of Windows bugs in handling LFNs whose SFN is identical
to the name of another file.  For example, Makefile.in.in has its SFN
as Makefile.in (when numeric tails are disabled), so if you have a
file called Makefile.in in the same directory, you are toast.  (For
another manifestation of the same bug, see the source of `_rename' in
the library.)

>    djgpppm -lfn
> or djgpppm --long-filenames

...and this is where the Makefile.in.in vs. Makefile.in will bite you.