Date: Fri, 07 Sep 2001 11:05:27 +0200
From: "H.Merijn Brand" <h DOT m DOT brand AT hccnet DOT nl>
To: Perl 5 Porters <perl5-porters AT perl DOT org>
Subject: Win2k + djgpp
Cc: djgpp-workers AT delorie DOT com
X-Mailer-Plugin: Cliche Inserter for Becky!2 Ver.0.03 Rev.0
Message-Id: <20010907105626.258A.H.M.BRAND@hccnet.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.00.07
X-Hops: 1
Reply-To: djgpp-workers AT delorie DOT com

I'm using the djgpp alpha port (2.04) for Win2000 supporting long names and
such, and is *much* more stable (at least on Win2k) than djgpp-203. bash-2.05
passes the whole Configure without dropping out, where bash-2.04 (even the 5
september port) still barfs out after a few seconds.

I'm now at the point that I can pass the default 'sh Configure -Dusedevel -des'
with full long-name support, but at the end (it takes over 20 minutes), there
*is* a config.sh, but *no* Makefile.

Browsing through Makefile.SH, I noticed that at the end it removes
$firstmakefile, being "makefile" (no caps). Since Win2k is still case
insensitive it removes the created Makefile :(

+ Is there a point in time where I have to define that the system has a case
  insensative file system?
+ Do I have to scan the Configure path (including the *.SH) for possible case
  conflicts?

-- 
H.Merijn Brand    Amsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.6.1, 5.7.1 & 629 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
  WinNT 4, Win2K pro & WinCE 2.11.  Smoking perl CORE: smokers AT perl DOT org
http://archives.develooper.com/daily-build AT perl DOT org/   perl-qa AT perl DOT org
send smoke reports to: smokers-reports AT perl DOT org, QA: http://qa.perl.org