Delivered-To: listarch-cygwin AT sourceware DOT cygnus DOT com 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 From: "Richard Stanton" To: Subject: Problem with make and executables in current directory Date: Wed, 10 Feb 1999 14:19:00 -0800 Message-ID: <000001be5543$5caf1360$943a85d1@CONNOR.berkeley.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal In-Reply-To: <36C1F8C1.EAE7E099@uni-duesseldorf.de> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 My PATH environment variable did not (until just now) include "." as one of its entries. Until recently, this caused no problems. Windows seems to look for executables in the current directory anyway, and I could use GNU make to compile and run C programs without needing to specify a directory. Just recently, however, GNU make has stopped being able to find executables in the current directory, unless "." is explicitly included in PATH. a. Is this behavior intentional? b. Rather stranger, why has it only just (last week or so) stopped finding executables in the current directory? This has not only happened to me (Windows 95), but also to a colleague running NT4. Both of us are almost 100% sure that it used to work until recently, and that we have not changed anything in our setups. This is all with Cygwin 20.1. Richard Stanton -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com