Date: Sun, 20 Aug 2000 08:27:24 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: kourino AT hotmail DOT com
Message-Id: <7458-Sun20Aug2000082724+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
CC: djgpp AT delorie DOT com
In-reply-to: <399EF0ED.9C55D71A@hotmail.com> (message from the Icefalcon on
	Sat, 19 Aug 2000 20:34:35 GMT)
Subject: Re: Fun with make and glibc
References: <399EC6ED DOT 5C058F8D AT hotmail DOT com> <8011-Sat19Aug2000211835+0300-eliz AT is DOT elta DOT co DOT il> <399EF0ED DOT 9C55D71A AT hotmail DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: the Icefalcon <kourino AT hotmail DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sat, 19 Aug 2000 20:34:35 GMT
> > 
> > Obviously, you need to install GNU Sh-utils (which will get you
> > echo.exe that can handle this command).  The error message you see
> > comes from COMMAND.COM's internal ECHO, which is too dumb.
> 
> Actually, I have :) But, since bash is so "nice" about passing stuff
> to DOS, it defaulted to DOS' echo instead of the one in /bin.

This cannot be true, unless you have a very old port of Make and/or
Bash.

Does the Makefile say "SHELL = /bin/sh" somewhere?  If not, this is
your problem.

Also, make sure the directory where you have all the utilities,
including Bash, is on your PATH, and that you have a sh.exe in that
directory.

> So, I went through Makefile and
> Makerules to change all the appropriate instances of echo to /bin/echo.

This shouldn't be necessary.  There's some other factor at work here.

> bash-2.03$ make
> Makefile:134: *** missing separator (did you mean TAB instead of 8
> spaces?).  Stop.
> bash-2.03$ 
> 
> Der .. line 134 of Makefile is:
> 
> all-Subdirs-files = $(wildcard $(addsuffix /Subdirs, $(config-sysdirs)))

This doesn't help at all, since you didn't say what $(config-sysdirs)
expands into.

> Oh, I went and changed the necessary "echo" statements in configure too.
> Didn't seem to make a difference.

It shouldn't.  I suggest to stop these random changes, since you can
easily break the scripts like that.