;>>>
>>>> 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
ll, cygwin env
>
> $make test
>
> test
>
> $make test2
>
> test
>
> $make test3
>
> fromtheenv
>
> $make test4
>
> fromtheenv
>
> $make test5
>
> fromtheenv
>
>
>
> --- linux --
>
> always working
>
>
&g
--
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
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, November 30, 2009 10:27
> To: bug-make
> S
: Monday, November 30, 2009 10:27
To: bug-make
Subject: not a bug but some strange behaviour
Hi!
I have a cygwin environment in which I've written a makefile, in this
environment it's working fine
I want to make it available to other dos user, so I've written a bat
file that set the cygwi
Hi!
I have a cygwin environment in which I've written a makefile, in this
environment it's working fine
I want to make it available to other dos user, so I've written a bat
file that set the cygwin path and call make,
in the doc env when I do
echo %somevar%
I see the correct result
however in comma
%% Oliver Schmidt <[EMAIL PROTECTED]> writes:
os> targA targB targC:
os> @echo "$@: T=<$T>"
os> T := 1
os> targA: T = 2
os> targA: T += 3
os> gives the output:
os> targA: T=<1 2 3>
os> In my opinion the output for targA should be "targA: T=<2 3>".
I agree, this looks like
Hi,
the following makefile:
Makefile start ===
.PHONY: targ targA targB targC
targ: targA targB targC
targA targB targC:
@echo "$@: T=<$T>"
T := 1
targA: T = 2
targA: T += 3
targB: T := 2
targB: T += 3
targC: T = 2
Makefile end ===
gi
Hello!
I've found a strange behaviour of make v3.79.1. A sample of the Makefile is
joined with this mail. The interesting part is the $(BASE) rule:
$(BASE): $(BASE).h $(OBJ2) $(OBJ1).o
@echo "it's okay..."
This rule indicate to generate $(BASE).h if
%% qun-ying <[EMAIL PROTECTED]> writes:
q> I want the object files to be placed in the object directory and latter
q> link against them.
You cannot use vpath/VPATH for this; that's not what it's for.
See my web site below for some details on VPATH and why it doesn't do
what you think.
--
Hi,
I have encounter this stragne behaviour. It is properly due to my
writing of the Makefile. But how do I solve this kind of problem?
I want the object files to be placed in the object directory and latter
link against them.
I am running make 2.79.1 under Linux 2.2.17 (slackware 7.1) with g
14 matches
Mail list logo
