RE: bug in cygwin build of Make

2004-01-15 Thread Rafael Kitover
>-Original Message- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Pearce >Sent: Thursday, January 15, 2004 1:25 PM >To: [EMAIL PROTECTED] >Subject: Re: bug in cygwin build of Make > [SNIP] > > >CVSVIEW= $(shell if [ -e CVS/Repository ]

Re: bug in cygwin build of Make

2004-01-15 Thread Jason Pearce
This indeed solves the problem and thanks for explaining the default shell issue. I actually thought that bash was used under cygwin, and I often construct syntax in a bash shell before using it in a makefile. It usually works but you've pointed out why there will be subtle differences. BTW the

Re: bug in cygwin build of Make

2004-01-15 Thread Robert Mecklenburg
JP> dir1/Makefile: JP> -- JP> VARIABLE = $(shell echo $$PWD) JP> JP> sources : JP> @echo VARIABLE set to ${VARIABLE} The GNU make variable CURDIR is set by make to the current working directory of the executing make. This is probably the variable you want. Hope this helps, -- R

Re: bug in cygwin build of Make

2004-01-14 Thread Christopher Faylor
On Wed, Jan 14, 2004 at 09:06:59AM +, Jason Pearce wrote: >I have discovered a problem in cygwin's Make. > >I am calling a sub-make that goes to another directory. That bit works >fine, but the Makefiles have a variable set from a shell command. That >shell seems to be spawned from the wrong