Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3D06268E.4DEC0A31@phekda.freeserve.co.uk>
Date: Tue, 11 Jun 2002 17:34:22 +0100
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: djgpp\config.bat, the arguments temp file and Windows NT
References: <3D0621AD DOT 76256C3A AT phekda DOT freeserve DOT co DOT uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Richard Dawe wrote:
> 
> Hello.
> 
> I've been trying to build Fileutils 4.1 under Windows NT 4 with SFN (no LFN
> TSR loaded). I discovered that it fails, because the temporary file
> arguments is created by Command Prompt, which can support LFNs. When
> config.bat tries to run configure like this:
> 
>     sh ./configure @arguments
> 
> it fails because sh can't arguments. It appears as argume~1 in 8+3.
[snip]

Slightly more fatal is the fact that we run sed to fix some things in
configure. Unfortunately the fixed configure script appears as config~1 in 8+3
and the original script is used instead.

Maybe we should rewrite djgpp\config.bat as a shell script. Then the shell
script would be running in the same environment as the tools and we'd avoid
these nasty SFN vs. LFN problems on Windows NT.

I'm guessing that not many people build packages on Windows NT 4!

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]