Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-ID: <37727AC7.B5F95A49@olf.com> Date: Thu, 24 Jun 1999 14:36:55 -0400 From: "Robert Bresner" X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin Subject: make 3.76 has path problems? (was Another clue into my problem with make...) References: <37714E16.69EF8DAE@olf.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit With this makefile: default: @path @echo PATH: $(PATH) NT E:\static\olf>make-3.76 PATH=c:\enscript; ... PATH: c:\enscript; ... NT E:\static\olf>make-3.75.exe make-3.75.exe PATH=c:\enscript; ... PATH: /enscript: ... NT E:\static\olf>make-3.75.exe --win32 PATH=c:\enscript; ... PATH: /enscript: ... make v3.76 is not always doing the 'right thing' with paths ? Which leads me to think that it is possibly responsible for knocking out my path during the complicated builds. Christopher Faylor wrote: > Any cygwin application changes the path from MS-DOS format to UNIX > format automatically, so this is not surprising. Again, the symptoms we experienced here happened without a recognizable pattern. Sometimes no problems, sometimes path = (null), sometimes path = unix-style-path. If unix-style-path is the right thing, then make 3.76 just isn't doing that, as shown with the very simple makefile example above.. Remarkable and indescribable thanks to you guys for helping me out. I never, ever, would have solved this problem on my own. ---------------------------------------- Robert Bresner rbresner@olf.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@sourceware.cygnus.com