Date: Mon, 10 Sep 2001 10:09:29 +0200 From: Laszlo Molnar To: djgpp-workers AT delorie DOT com Cc: "'Perl 5 Porters'" Subject: Re: Win2k + djgpp Message-ID: <20010910100928.K3069@libra.eth.ericsson.se> References: <20010907105626 DOT 258A DOT H DOT M DOT BRAND AT hccnet DOT nl> <000101c137cd$948d5c00$907d76d5 AT pandora DOT be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <000101c137cd$948d5c00$907d76d5@pandora.be>; from tim.van.holder@pandora.be on Fri, Sep 07, 2001 at 08:47:44PM +0200 Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > > 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 :( > It's been a while since I configured Perl, but isn't $firstmakefile > supposed to be GNUmakefile when using GNU make? That's right. GNUmakefile is the makefile that is used. > > + Do I have to scan the Configure path (including the *.SH) > > for possible case conflicts? > That's always a good idea, but I thought Perl was already pretty > good with respect to 8+3 compatibility, so there shouldn't be many > such issues. It was possible to build perl on 8.3 systems (I usually built it under linux + dosemu with short file names). Unfortunately with the addition of the Encode module it's no longer possible to build perl without long file names. [Well, it was not possible 2 months ago when I last checked.] ml