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: <37714E16.69EF8DAE@olf.com> Date: Wed, 23 Jun 1999 17:13:58 -0400 From: "Robert Bresner" X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin Subject: Another clue into my problem with make... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Howdy again The new details: 1. Before, my make problem was limited to emacs, but I've been informed that the problem exists in an NT cmd.exe session as well ( but not on my machine. ) Could this be an environment thing? (What environment variables are used by make? I know SHELL. Is WORK? Of the 2 books I have on make, only one mentions SHELL. ) 2. Before, the PATH was getting _blown away_ [ PATH=(null) ], but I've now seen where an NT style path (e.g. w:\my_path) is being changed to a *nix style path, after an NT mount (e.g. //w/my_path). That is just incredibly odd. Does GNU make check the Cygwin mount table? The Recap: NT4 SP1-5 Cygwin 20.1 (?) and/or cygwin1-19990115.dll ( but this problem has existed for years, across several installations ) GNU Make version 3.76.1 The Problem: During a very large and complicated make induced build, the PATH is arbitrarily lost, so various tools in the build cannot be found and executed, thus the build fails. The original details: By arbitrarily, I mean that a) it doesn't happen to everyone. b) it doesn't always happen. I cannot establish a pattern beyond the fact that it _usually_ happens after a certain Perl script runs, but not always, and within a relatively few directories ( the whole build is about 130 directories building some 2 million lines of code ), but not always. The Perl script has been extensively checked and double- checked by the resident Perl gurus, and it is not the cause of the problem (also confirmed by the fact that it runs with no problems in 128 other dirs, on various platforms, on 80 other machines). Hoping the new details will jog a memory for someone. This wouldn't be such an issue, except that it is worse for some people than others, and the problem has been spreading. (Up to 6 people who occasionally experience it, and one fellow has it happen _every day_. He's the most vehement about finding a solution, as one might imagine. ) Thanks in advance for any help... ---------------------------------------- Robert Bresner rbresner AT olf DOT com Open Link Financial 516-227-6600 x216 http://www.olf.com/ fax: 516-227-1799 ---------------------------------------- Opinions expressed are explicitly my own "No more talking! Cerebus has a SWORD!" -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com