Mail Archives: djgpp/2000/08/20/01:25:17
> 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.
- Raw text -