Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Tue, 11 Apr 2000 17:00:52 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Cc: mdejong AT cygnus DOT com Subject: Re: "make" seems to be broken on Win95. Message-ID: <20000411170052.H2717@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com, mdejong AT cygnus DOT com References: <200004112054 DOT PAA15038 AT hp2 DOT xraylith DOT wisc DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <200004112054.PAA15038@hp2.xraylith.wisc.edu>; from khan@NanoTech.Wisc.EDU on Tue, Apr 11, 2000 at 03:54:04PM -0500 I should also point out that discussions about 'make' are off-topic for this mailing list. Take a look at the cygwin mailing list web page for what is considered on-topic. cgf On Tue, Apr 11, 2000 at 03:54:04PM -0500, Mumit Khan wrote: >Mo DeJong writes: >> Hi all. >> >> I just tired to build the installer from the CVS when >> I ran into a problem with make. Cygwin's version of >> make pukes out if the case of a file differs from >> what is expected in a build rule. Here is a quick >> example. >> >> BASH.EXE-2.03$ ls >> MER.C Makefile error.c >> >> BASH.EXE-2.03$ cat Makefile >> SHELL=/bin/sh >> >> %.o: %.c >> @echo converting $? to $@ >> >> all: error.o mer.o > >DJ already talked about this, so I'll just point out two quick items: > >- Make already has a (compile-time) provision for using case insensitive > filenames, but it breaks implicit rules in a horrible way. Is MER.C a > C++ file or is it a C file? Does the FOO.F file need to pre-processed > or is it really just `foo.f'? Please remember that most of the tools > are just repackaged Unix tools, and lots of Unix'ism is buried quite > deep (eg., gcc's use of the filename extensions). > >- Issues like this belong in the general list since this is more of an > "user tool" issue rather than the underlying API issue. > >The Cygwin mailing list has seen this discussion quite a few times before >and should have it archived. It should be pretty easy to provide a command >line or an env variable to choose this behaviour at runtime.