Date:	Tue, 27 Jul 1999 09:45:01 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Jeff Hammond <jshammond AT my-deja DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Cross-compiler on NT without bash lfn support?
In-Reply-To:	<7nic38$rg7$1@nnrp1.deja.com>
Message-ID:	<Pine.SUN.3.91.990727094440.5354G-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 26 Jul 1999, Jeff Hammond wrote:

> It looks like a LFN problem with bash only, LFN works on
> the DOS window before bash is invoked.

LFN seems to work before Bash is invoked, because you use the NT
shell, which is a Windows console program.  No DJGPP program can
access the long file names on NT, either from Bash or from another
shell.  This means that Make, GCC, the linker, and all the other tools
compiled with DJGPP will not be able to see the long names.

> The mail archives say that bash on NT does not support LFN and the FAQ
> says that I need LFN to rebuild gcc from source.  Is there a way around
> these constraints so that I can create a cross compiler on NT?

The way around is to do the necessary mundane work to solve the
problems that prevent you from building the cross-compiler.  Solving
these problems shouldn't be rocket science, as most DJGPP packages
already can be built without long file names.  If you want to pursue
this route, please report here any problems you have, and you will get
help.

- Raw text -