Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 4 May 2005 13:40:34 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: pwd vs $PWD, bash, cygwin vs Linux Message-ID: <20050504174034.GV24661@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050504160421 DOT GQ24661 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i To clarify: 1) The correct long-term solution to the problem of bash/ash incompatibilities is to modify the makefile to avoid the problem. If the Makefile is yours, then you are done. If the makefile is from someone else, then you provide the someone else with a patch. If you can be guaranteed that you are using GNU make then you can use "$(CURDIR)" in place of $$PWD. Otherwise, you'll need to use `pwd`. 2) The easiest workaround to the problem is "make SHELL=/bin/bash". I did not suggest this originally because I thought that the makefile was home-grown and would benefit from being permanently fixed. This has the drawback of requiring you to remember to do this every time you type "make" which is somewhat of a problem if you are doing active development. 3) When I said "shirley you don't intend" I was parodying the poster who was appalled by the idea of modifying the thousands of makefiles out there which just must be rife with the use of PWD. It was not a serious comment, since if you are going to modify your makefile to say "SHELL = /bin/bash" you might as well just modify your makefile to use CURDIR. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/