Subject: Re: Win2k + djgpp From: Tim Van Holder To: djgpp-workers AT delorie DOT com Cc: Laszlo Molnar , Perl 5 Porters , "H.Merijn Brand" In-Reply-To: <20010910110744.4ABF.H.M.BRAND@hccnet.nl> References: <000101c137cd$948d5c00$907d76d5 AT pandora DOT be> <20010910100928 DOT K3069 AT libra DOT eth DOT ericsson DOT se> <20010910110744 DOT 4ABF DOT H DOT M DOT BRAND AT hccnet DOT nl> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13.99+cvs.2001.09.07.02.46 (Preview Release) Date: 10 Sep 2001 16:22:41 +0200 Message-Id: <1000131770.23270.13.camel@bender.falconsoft.be> Mime-Version: 1.0 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 On Mon, 2001-09-10 at 11:12, H.Merijn Brand wrote: > On Mon 10 Sep 2001 10:09, Laszlo Molnar wrote: > > > > 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. > > but that is set from the hints file, and since I'm running from Win2k with > alpha djgpp it did not recognize the combination and thus did not use those > hints :( Hmmm - neither win2k nor the fact that you use a CVS libc should affect that (I think) - it should still find dos-djgpp as system. What does 'uname -a' print? > Just for the record, I'm trying to build with *long* names on Win2k with alpha > djgpp-2.04 LFN issues should be irrelevant to case sensitivity issues. Since cygwin is also a case-insensitive environment, I expect any such problems have long been ironed out. > I got rid of some core dumps and other inconveniences. One major show stopper > is that Configure can't read from input (every letter typed is immediately > returned as answer), so I have to put all my answers in the Policy.sh That's most likely a bash issue (possibly related to stdin seeks or termcap).