Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <389B8A47.1423291E@cygnus.com> Date: Fri, 04 Feb 2000 18:26:15 -0800 From: Eric Christopher X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: earnie_boyd AT yahoo DOT com CC: cygwin AT sourceware DOT cygnus DOT com, cgf AT cygnus DOT com Subject: Re: MAKE_MODE=UNIX? was RE: why must cygwin be first in path? References: <20000205012729 DOT 24488 DOT qmail AT web115 DOT yahoomail DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Earnie Boyd wrote: > > --- Eric Christopher wrote: > -8<- > > While I'm on this type of bent, does anyone have an opinion on making > > the filesystem case insensitive by default for MAKE_MODE = win32? > > Alternately it could be a flag or something. Just wondering what people > > thought. > > Have you really thought about this? Gcc cares about case of the filename, > especially some suffixes. Besides, bash supports switches for > case-insensitivity; I don't know though if the same is true for ash. > Yeah, that's why I'm asking. :) It was more of a question for people who use win32 mode from within cmd.exe. Almost sounds like a mingw32 type addition as opposed to a cygwin addition. -eric -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com