Message-ID: <36377206.52B5501C@montana.com>
Date: Wed, 28 Oct 1998 12:35:34 -0700
From: bowman <bowman AT montana DOT com>
X-Mailer: Mozilla 4.5b2 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: Recursive make: portable technique?
References: <Pine DOT SUN DOT 3 DOT 91 DOT 981027201412 DOT 8711C-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com



Eli Zaretskii wrote:
> 
> Since there's no such magic on DOS/Windows, Make must chdir back when
> the commands it invoked exit, if it wants to restore the original
> directory.  The DJGPP port of Make indeed does that, but only when
> Make itself is about to exit (so you wind up in the same place where
> you invoked Make); that is why "make -C foo" works in recursive
> sub-makes.



ah! that was what was confusing me.

starting from 

C:\TEST>make 

make runs some of the makefile, and after the cd, says:

make.exe[1]: Entering directory ......

it the runs that  makefile, and says

make.exe[1]: Leaving directory ........

but then 'copy' reports 'Path not found', the rest of the makefile, a
link, fails,
resulting in 

make.exe: *** [all] Error 1.

C:\TEST>

So, looking at that, it looked like it had entered and left the
subdirectory, and when
it failed, it was actually back in the original directory. 

A little confusing, but now I know enough to scan for any suspicious
'cd' commands
in the makefiles and change them to the -C command for DOS
compatibility.

thanks again,  bob