;>>>
>>>> This program built for i686-pc-cygwin
>>>>
>>>> $
>>>>
>>>>
>>>>
>>>> The exact test case I used wasn't quite the same as you gave:
>>>>
>>>>
>>>>
>>>&
gt; $ cat make.bat
>>>
>>> C:\cygwin-1.5\bin\make %*
>>>
>>> $ cat Makefile
>>>
>>>
>>>
>>> export TEST_FLAG=test
>>>
>>> SHELL=/bin/bash
>>>
>>>
>>>
>>> test :
>>
;> printf "${TEST_FLAG}\n"
>>
>>
>>
>> test3 :
>>
>> printf "$${ENV_VAR1}\n"
>>
>>
>>
>> test4 :
>>
>> printf "${ENV_VAR1}\n"
>>
>>
>>
>> test5
t;
> test4 :
>
> printf "${ENV_VAR1}\n"
>
>
>
> test5 :
>
> ENV_VAR1=${ENV_VAR1}; /bin/bash somescriptthatdoprintfenv_var1
>
>
>
>
>
> $
>
>
>
> If I had make.bat run "make", then it ended up invoking itself. My
printf "${TEST_FLAG}\n"
>
>
>
> test3 :
>
> printf "$${ENV_VAR1}\n"
>
>
>
> test4 :
>
> printf "${ENV_VAR1}\n"
>
>
>
> test5 :
>
> ENV_VAR1=${ENV_VAR1}; /bin/bash somescriptthatdoprintfenv
--
From: jean-luc malet [mailto:jeanluc.ma...@gmail.com]
Sent: Monday, November 30, 2009 14:27
To: Martin Dorey
Cc: bug-make
Subject: Re: not a bug but some strange behaviour
$cat make.bat
set PATH=cygwin_Path;oldPath
make %*
$ cat /tmp/Makefile
export TEST_FLAG=test
SHELL=/bin/bash
$cat make.bat
set PATH=cygwin_Path;oldPath
make %*
$ cat /tmp/Makefile
export TEST_FLAG=test
SHELL=/bin/bash
test :
printf "$${TEST_FLAG}\n"
test2 :
printf "${TEST_FLAG}\n"
test3 :
printf "$${ENV_VAR1}\n"
test4 :
printf "${ENV_VAR1}\n"
test5 :
ENV_VAR1=${ENV_VAR1}; /bin/bash somescriptt
Can you contrive a simple test case - something that you can post here in its
entirety to help someone reproduce the problem?
-Original Message-
From: bug-make-bounces+mdorey=bluearc@gnu.org
[mailto:bug-make-bounces+mdorey=bluearc@gnu.org] On Behalf Of jean-luc malet
Sent: Monday
