:
run all shell wrapper through sh
put SHELL = sh
now it seems to work fine... result in 4h of build...
thanks for the support
JLM
On Tue, Dec 1, 2009 at 2:53 PM, jean-luc malet wrote:
> almost
> it seems that it fixe the shell script but if I call some dos tool
> inside, then the env is
/tmp/cmd.file
sh$ echo make.bat test >> /tmp/cmd.file
sh$ cat /tmp/cmd.file; #all is ok
so it seems really related to the fact that make behave differently if
launched in a cmd or if somewhere else before a cygwin session as been
created
On Tue, Dec 1, 2009 at 11:44 AM, jean-luc malet
JLM
On Tue, Dec 1, 2009 at 11:05 AM, jean-luc malet wrote:
> in the bat file you have to do
> call path\to\the\real\make.exe %*
> you might also want to use the -f option of make to have it using the
> right makefile
> JLM
>
> On Mon, Nov 30, 2009 at 11:58 PM, Martin Dorey
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
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
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
t; then rename all the remaining targets, variables and files, then you'll end
> up with an example that you can send us. I've done that on a number of
> occasions for compiler bugs and, while I can attest that it's tedious work,
> it rarely takes longer than, say, an hou
hello from component/Makefile
>
> make[1]: Entering directory `/home/martind/tmp/make-jpm/component'
>
> make[1]: `default' is up to date.
>
> make[1]: Leaving directory `/home/martind/tmp/make-jpm/component'
>
> mart...@whitewater:~/tmp/make-jpm$
>
>
>
I don't know if this reached the list (sent before aknowledge of mailman)
-- Forwarded message --
hi!
I face issue when using MAKEFILES variable
this variable is set into a toplevel makefile and contain only
export varname=varvalue
lines
then submake is called into rules
hi!
I face issue when using MAKEFILES variable
this variable is set into a toplevel makefile and contain only
export varname=varvalue
lines
then submake is called into rules like this
target :
MAKEFILES=theconffile ${MAKE} -C the/component/path -f Makefile target
into the/compone
11 matches
Mail list logo
