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: Sun, 9 Feb 2003 18:30:28 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Shell brace expansion in make works? Message-ID: <20030209233028.GA30989@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030209151057 DOT A13079 AT saturn DOT billgatliff DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Sun, Feb 09, 2003 at 04:28:21PM -0500, Rolf Campbell wrote: >William A. Gatliff wrote: >>I have a Makefile with a command like this: >> >> mkdir -p /opt/billgatliff/{usr,lib} >> >>Works fine under Linux, but not on the latest Cygwin. >> >>Under Cygwin, what I actually get is a directory called "{usr", >>instead of "usr". Other variations on this brace expansion (in tar >>arguments, etc.) produce similar problems. >> >>I checked this: >> >>$ set | grep SHELL >>SHELL=/bin/bash >> >>Seems fine. But when I do this: >> >>$ make SHELL=/bin/sh ... > ^^ "bash" >> >>I actually get what I'm after, i.e. "usr" instead of "{usr". >I'm guessing that you meant to type "bash" in the email. Either way, >cygwin make seems to ignore the environment variable SHELL, and uses >'/bin/sh' unless you specify on the command-line or in the makefile. Yeah, cygwin's make, and linux's make, and Tru64's make, and... Since /bin/sh is "ash" on cygwin and brace expansion is not supported in ash, this is working as designed. cgf -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam AT sourceware DOT org and be permanently blocked from mailing lists at sources.redhat.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/