This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: gmake MAKE_MODE problem



Pfff, found it:

had to unset a number of environment variables that were
sneakily set by gmake:

set TERM=
set SHELL=
set MAKEFLAGS=
set MFLAGS=




----- Original Message ----- 
From: "Erwin Kalvelagen" <erwin.kalvelagen@verizon.net>
To: <cygwin@cygwin.com>
Sent: Thursday, July 19, 2001 8:46 PM
Subject: gmake MAKE_MODE problem


> 
> 
> Hi:
> 
> I have a problem with gmake related to the MAKE_MODE environment variable.
> We have a large gmake system that is using and relies on MAKE_MODE=UNIX.
> A new subsystem calls gmake from this but it wants MAKE_MODE=DOS so
> that no backslashes are lost. Basically what we do is:
> 
> Makefile:
> ---------------------------------------------------------------------------
> # assume this makefile is called with MAKE_MODE=unix
> 
> SHELL=/bin/sh
> 
> all:
>  echo $(MAKE_MODE)
>  ./batch.bat
> ----------------------------------------------------------------------------
> 
> Batch.bat:
> ----------------------------------------------------------------------------
> set MAKE_MODE=dos
> gmake -f Makefile2
> ----------------------------------------------------------------------------
> 
> Makefile2:
> ----------------------------------------------------------------------------
> all:
>  command.com /c echo $(MAKE_MODE)
>  command.com /c echo c:\windows
> ----------------------------------------------------------------------------
> 
> The output of running gmake shows:
> 
> 
> F:\visbuild\problem>gmake
> echo unix
> unix
> ./batch.bat
> 
> F:\visbuild\problem>
> F:\visbuild\problem>set MAKE_MODE=dos
> 
> F:\visbuild\problem>gmake -f Makefile2
> command.com /c echo dos
> dos
> command.com /c echo c:\windows
> c:windows     <-------------------- !!!!!!!!!!!
> 
> F:\visbuild\problem>
> 
> 
> I.e. although MAKE_MODE is set to DOS the second invocation of gmake 
> does not treat a backslash properly. 
> 
> 
> Interestingly if I call BATCH.BAT directly from the command line I get:
> 
> F:\visbuild\problem>batch
> F:\visbuild\problem>set MAKE_MODE=dos
> 
> F:\visbuild\problem>gmake -f Makefile2
> command.com /c echo dos
> dos
> command.com /c echo c:\windows
> c:\windows  <-------------------- !!!!!!!!!!!
> 
> F:\visbuild\problem>
> 
> 
> Is there another environment variable that the second invocation inherits
> from the first that needs to be reset to make sure that a \ is not considered
> as an escape character?
> 
> 
> Thanks, Erwin
> 
> 
> 
> 
> 
> --
> 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/


--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]