Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <375EBF83.2BB6CF98@dddandr.octacon.co.uk> Date: Wed, 09 Jun 1999 20:24:51 +0100 From: Don Sharp Reply-To: dwsharp AT iee DOT org X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: "Brown, Kim" CC: "'Blob, Dave'" , "'cygwin AT sourceware DOT cygnus DOT com'" Subject: Re: Problem with make References: <9F481A71957AD111BB2300805FE65D2504749D32 AT mpisex02 DOT mops DOT wl DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Brown, Kim wrote: > > I have found GNU make to be buggy with some makefiles, especially those > generated by PERL install packages. I just use nmake from microsoft without > problems. Anyone else have problems with GNU make? > Yes. I am currently trying to isolate a test case to demonstrate a bug (in 3.77) which takes the form of showing the right set of commands to execute when you do a make -n target without the -n it then tries a build of the dependencies using the built-in rules, overriding any rules in the Makefile, even if the dependencies don't need to be re-built. The main point of interest is that the target must be specified within a Make variable like TARGET = me target DEPENDENCY = son $(TARGET): $(DEPENDENCY) throw $@ and son out of the bar at midnight and you do a make me for instance. Cheers Don Sharp > > > > Ok, this is a wierd one, so bear with me. > > > > I've been using cygwin to do some java development with a > > coworker. For a > > while, we were just doing "jikes *.java", and had no problems. As the > > project grew, we split things into packages and added > > Makefiles to build the > > whole project. The problem that showed up was that it worked > > for me, but > > not for him - he'd get an error message each time that said "jikes - > > permission denied". The same command that make was trying to > > execute worked > > from the command line though... Perplexing. We switched to > > javac - worked > > fine. > > > > Anyhow, Turns out that in the directory where jikes.exe is, he had a > > directory named jikes also - make was trying to execute it, > > but bash wasn't. > > > > > > So obviously, this is a bug in make - it must be looking for > > a program named > > jikes before jikes.exe - I guess. Either that, or it's not > > checking to make > > sure it's a directory when it checks. I don't mind tracking > > this one down > > and submitting a bug fix, but I thought I ought to find out > > if it's been > > heard of or fixed, etc. > > > -- > Want to unsubscribe from this list? > Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com