Date:	Sun, 25 Oct 1998 19:47:55 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	bowman <bowman AT montana DOT com>
cc:	"djgpp AT delorie DOT com" <djgpp AT delorie DOT com>
Subject:	Re: Recursive make: portable technique?
In-Reply-To:	<362FF086.BDA6266C@montana.com>
Message-ID:	<Pine.SUN.3.91.981025194736.24396N-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Thu, 22 Oct 1998, bowman wrote:

> On a straight DOS system with only command.com for a shell, make will
> fail after
> 
> cd ../new_dir; $(MAKE) 
> 
> I found that doing an explicit  cd ../original_dir fixed the problem,

This is a feature.  Many DOS Makefiles expect Make to remain in a
directory where it chdir'ed (because most DOS versions of Make don't
support multiple commands on a single line, like in the above
example), and all DJGPP ports support this as well.

> So, my question, is the explicit cd safe in all configurations, or will
> I get burnt?

I don't understand what ``explicit cd'' are you talking about, but in
general, you can force Make to use a certain shell by defining SHELL
in the Makefile.

- Raw text -