Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: M4um@aol.com Message-ID: Date: Mon, 18 Dec 2000 12:10:27 EST Subject: Re: #includes not being processed across network To: cygwin@cygwin.com CC: lhall@rfk.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Windows AOL sub 109 Dear Sir: In response to: >>Found: D:\Cygwin\bin\sh.exe >>Warning: d:\BIN\sh.exe hides D:\Cygwin\bin\sh.exe >>Found: \bin\sh.exe >>Warning: d:\BIN\sh.exe hides \bin\sh.exe >Its not at all obvious that d:\bin\sh.exe is equivalent to >d:\Cygwin\bin\sh.exe. Is it? If so, for maintainability reasons, >I'd recommend either using a mount or symbolic link or something to >get a sh.exe into /bin. The two copies of sh.exe are identical. You'll note my comment in the stream immediately after your comment which says: "(***NOTE: The two copies of sh.exe above are identical.)" Until I get the compiler working across the net, I am avoiding the use of links just to make sure that they don't complicate the problem. Thanks, John McDonald -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple